User forums > Using Code::Blocks
My issues with C::B (for real now :)
oZZ:
I've been using C::B for almost two weeks now after coming from Eclipse CDT. C::B is easily my favourite IDE, and you guys have done an amazing job! I'm listing some improvements that I think will make C::B even better. Some of these are bugs that may (most likely) or may not be known about already.
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.
2. "export makefile" is greyed out?
3. Symbol search is disabled (obviously known about)
4. Symbol view can't sort by type. Being able to view only methods while in "this file's view" would be really nice.
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.
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.
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. This means if the source file has an error that requires modification of the header then you have to recompile all files up to the source file. This wastes *A LOT* of time. Ideally I think it should check the header, compile the source, then if no errors, recompile everything.
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.
This is a list of bad things about C::B, I don't think I could possibly type a list of all the things I love about C:B because it would take too long. Keep up the amazing work, and I hope some of these things are being looked at!
-Shawn
mandrav:
--- Quote ---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.
--- End quote ---
Symbols browser needs nothing from the data folder...?
--- Quote ---2. "export makefile" is greyed out?
--- End quote ---
Yes, this option is not available at the moment.
--- Quote ---3. Symbol search is disabled (obviously known about)
--- End quote ---
Correct.
--- Quote ---4. Symbol view can't sort by type. Being able to view only methods while in "this file's view" would be really nice.
--- End quote ---
File a feature request if you like. I trust you 've seen the code-completion toolbar (yes, a misnomer, I know)?
--- Quote ---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.
--- End quote ---
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.
--- Quote ---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.
--- End quote ---
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.
--- Quote ---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.
--- End quote ---
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.
--- Quote ---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.
--- End quote ---
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.
Belgabor:
--- Quote from: mandrav on October 13, 2006, 04:08:51 pm ---
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.
--- End quote ---
This also bothered me. Mainly because I've seen it work sometimes and sometimes not (success rate for me was way below 95%).
So I did a short test and I think I stumbled across a bug. It seems to work pretty reliably if you use code completion to complete the function name. If you type it out yourself, it pretty reliably DOESN'T work.
killerbot:
--- Quote from: Belgabor on October 13, 2006, 04:25:51 pm ---
--- Quote from: mandrav on October 13, 2006, 04:08:51 pm ---
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.
--- End quote ---
This also bothered me. Mainly because I've seen it work sometimes and sometimes not (success rate for me was way below 95%).
So I did a short test and I think I stumbled across a bug. It seems to work pretty reliably if you use code completion to complete the function name. If you type it out yourself, it pretty reliably DOESN'T work.
--- End quote ---
if possible try to provide mini projects or source files where things are reproducable
Belgabor:
Very Easy:
--- Code: ---#include <string.h>
void test() {
}
--- End code ---
Go into the function, type "memcpy(" -> nothing shows up.
Go into the function, type "memc", select "memcpy" from the list, type "(" -> parameters show up.
Edit: ok, not very easy :( seems to work in a new project
Edit2: I'm currently unable to work this out as the assertion error (I think it was mentioned in the 11th Oct. nightly thread) keeps popping up. But now the error shows up again as described in a fresh project with one cpp file filled as above (corrected).
Navigation
[0] Message Index
[#] Next page
Go to full version