1. Symbol browser loses all symbols occasionally. To fix it I delete the application data folder, but I'm able to save the preference file, and restore it after C::B generates a new app data folder.
Symbols browser needs nothing from the data folder...?
2. "export makefile" is greyed out?
Yes, this option is not available at the moment.
3. Symbol search is disabled (obviously known about)
Correct.
4. Symbol view can't sort by type. Being able to view only methods while in "this file's view" would be really nice.
File a feature request if you like. I trust you 've seen the code-completion toolbar (yes, a misnomer, I know)?
5. Code complete should show types, (and names if defined in the header) of arguments to calling functions. ie: someObj->fun( <- at this point show above the cursor: "(int some_arg_name, char *whatever)" just like Visual Studio.
Usually, when I see "just like your_fav_other_ide" in a sentence I close the firefox tab
.
This functionality is implemented already. It could be that in some cases it won't work but the same goes for code-completion as a whole. It's working correctly 95+% of the time and that's good enough based on my original goals.
6. when closing a window (ctrl-w) it should bring you to the window you last had open, not the previous one in the window list.
Just yesterday, we updated the notebook control and allows tabbing between the open files the way you said. Closing is not following this principle though. But since Eran, the author of that control, is a frequent visitor here, I guess he 'll like this idea and possibly implement it.
7. when you change a header file and a source file and recompile it checks the header file for syntactic accuracy, but not the source file before it recompiles the dependant sources.
No such check is made. When you hit "Build" the build process starts. Each file is compiled when its time comes.
If you want to verify that your changes are not build-breakers, hit Ctrl-Shift-F9 ("Compile file") first and then hit "Build". There are plans to add a "Check syntax" option but it's obviously not implemented yet.
8. Stack trace is incomplete on debugger. It shows the exact line of a crash, however it only shows the first 3-4 functions in the stack trace. Eclipse CDT with the *EXACT* same gdb shows much more information in the stack trace.
I 've heard this before and I don't know what to make of it... Really, we only output what gdb prints. The only reason I can think of for this to fail, is if one of the regular expressions misses some lines. Do us a favour and give more info when this happens again to you:
- Enable the debugger's *debug* log in the options.
- When you notice that the backtrace is missing lines (check the first column "Nr." and look for discrepancies), turn to the debugger's debug log and copy/paste its output in a post here so I can have a look.
Yiannis.