sry, that i havn´t answered the last days...
The own big thing I miss is the editor opens automatically included source files.
this will be added in RC3, coming this week
Also the Error-Finding works not always right Often the editor underline my code, although it compiles correctly and works fine in tests.
this is a bug in the used c-grammar. the problem is if the code starts like a cast a wrong shift is performed. for example "(time_step*4+7)" is treated as an error. adding a 0 in front "(0+time_step*4+7)" can avoid this problem. but that´s no long-time solution.
there seems to be another bug, but in the parsing-engine (not developed by me). if the file ends with a singleline-comment or a preprocessor-directive, the parser reports an error in the syntax. a newline can solve this issue.
i´m working on both issues
But it's still my favorite IDE.
thanks, this is nice to hear
