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.
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.
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.
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.
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.
#include <string.h>
void test() {
}
Go into the function, type "memcpy(" -> nothing shows up.Yes, in this case, you have to press Ctrl+Shift+Space to get the call tip. But Ctrl+Shift+Space doesn't work, if you've already closed the parentheses.
Indeed, you're right. But I still don't get why it behaves differently, as you have to type the '(' yourself in both cases...Quote from: BelgaborGo into the function, type "memcpy(" -> nothing shows up.Yes, in this case, you have to press Ctrl+Shift+Space to get the call tip. But Ctrl+Shift+Space doesn't work, if you've already closed the parentheses.
A maximize window button that makes the code window take the full C::B window. The text zoom is really nice, but having code take up the whole window would be a great addition I think. In Eclipse ctrl + numkey enter toggles the maximization of a window.
I did a quick test using my existing project and the debugger's stack trace in the log is more complete than the window.
QuoteA maximize window button that makes the code window take the full C::B window. The text zoom is really nice, but having code take up the whole window would be a great addition I think. In Eclipse ctrl + numkey enter toggles the maximization of a window.
View->Fullscreen
#include <iostream>
#include <vector>
struct three
{
three() { f_vec.resize(200); }
int a, b, c, d, e, f, g;
float h, i, j, k, l, m, n;
std::vector<float>f_vec;
};
struct one
{
one() { p = new int; *p = 5; t = new three;}
~one() { delete p; delete t; t = 0; delete t; t->a = *p; }
int *p;
three *t;
};
struct two
{
two() { o = new one; }
~two() { delete o; }
one *o;
};
void f()
{
two *t = new two;
std::cout << *(t->o->p) << std::endl;
delete t;
}
int main()
{
f();
return 0;
}
Ah, thanks. Obviously the regular expression can't handle two sets of parentheses. I 'll fix it real soon.