User forums > Using Code::Blocks

My issues with C::B (for real now :)

<< < (2/4) > >>

bigbug:

--- Quote from: Belgabor ---Go into the function, type "memcpy(" -> nothing shows up.
--- End quote ---
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.

oZZ:
Symbols browser needs nothing from the data folder...?

I know it doesn't, but I think the process of regenerating it fixes the bug.  I can't really explain it more than that, but I've observed this at least three times.

Belgabor:

--- Quote from: bigbug on October 13, 2006, 04:50:19 pm ---
--- Quote from: Belgabor ---Go into the function, type "memcpy(" -> nothing shows up.
--- End quote ---
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.

--- End quote ---
Indeed, you're right. But I still don't get why it behaves differently, as you have to type the '(' yourself in both cases...

oZZ:
Oh, one more thing I forgot to add to my list ;)

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.

(edit)...and another =)

Can't easily generate files in a particular folder.  Should be able to right click folder and go "new file" and choose C++ header/source or class or other possible options, (especially when viewing in filesytem tree mode).  Right now I've found the most efficient way to do it is to make new files in windows explorer then import them.

Also I'm trying out the debugger right now with a simple example (deleting something twice) through 10 function calls, then I'll try recursion and see what it does.

oZZ:
Ah ha!

I did a quick test using my existing project and the debugger's stack trace in the log is more complete than the window.

Here's the debug log:
#0  0x0b69f4a1 in ?? ()
#1  0x0040216a in Entity::~Entity() (this=0xb69f718) at Framework/Bases/Entity.cc:86
#2  0x0057cd39 in Menu::~Menu() (this=0xb69f718) at Framework/Menus/Menu.cc:23
#3  0x00574cc9 in ConfigMenu::~ConfigMenu() (this=0xb69f718) at Framework/Menus/ConfigMenu.cc:2409
#4  0x0053d090 in EntityManager::process() (this=0xb60c7b0) at Framework/Managers/System/EntityManager.cc:217
#5  0x005bfbe1 in Rainbow::mainLoop() (this=0xb5f36f8) at Game/Bases/Rainbow.cc:111
#6  0x0060a6e9 in SDL_main (argc=1, argv=0x22fe60) at Game/main.cc:60
#7  0x0060d940 in console_main (argc=1, argv=0x22fe60) at win32/SDL_win32_main.c:249
#8  0x0060db05 in WinMain (hInst=0x400000, hPrev=0x0, szCmdLine=0x251f23 "", sw=10) at win32/SDL_win32_main.c:361
#9  0x0060d43a in main ()

The window shows NR: 0, 6, 7, 8, 9.
Numbers 1, 2, 3, 4 and 5 are missed. The only thing those lines seem to have in common is the argument after the function name is this=<something>...

Navigation

[0] Message Index

[#] Next page

[*] Previous page