Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
unused varibles in manager.cpp - wxAUI
mandrav:
--- Quote from: 280Z28 on January 14, 2006, 07:36:43 pm ---Code::Blocks really doesn't like having wxWidgets in debug mode :(
--- End quote ---
And what exactly does that mean Sam? What does C::B has to do with wxASSERT_MSG() and the fact that it expands to nothing when in release mode?
280Z28:
--- Quote from: mandrav on January 14, 2006, 08:37:26 pm ---
--- Quote from: 280Z28 on January 14, 2006, 07:36:43 pm ---Code::Blocks really doesn't like having wxWidgets in debug mode :(
--- End quote ---
And what exactly does that mean Sam? What does C::B has to do with wxASSERT_MSG() and the fact that it expands to nothing when in release mode?
--- End quote ---
It throws a TON of assertions, so many that you can't get very far into the program before it's just too much to write them down. I put a patch on SF that gets rid of some but not all of them.
https://sourceforge.net/tracker/index.php?func=detail&aid=1400615&group_id=126998&atid=707418
I'm talking about having the wxWidgets library itself in debug mode, so all the wxASSERT_MSG() calls in it start popping up. Not the ones in the C::B code.
Game_Ender:
--- Quote from: 280Z28 on January 14, 2006, 08:45:58 pm ---It throws a TON of assertions, so many that you can't get very far into the program before it's just too much to write them down. I put a patch on SF that gets rid of some but not all of them.
https://sourceforge.net/tracker/index.php?func=detail&aid=1400615&group_id=126998&atid=707418
I'm talking about having the wxWidgets library itself in debug mode, so all the wxASSERT_MSG() calls in it start popping up. Not the ones in the C::B code.
--- End quote ---
Isn't it standard development progress to always be running against the debug libraries? Then when ready for final compile against the release builds? Although I admit this can be hard because it looks like codeblocks project wasn't set up with this kind of development in mind.
As a wxWidges dev myself It can be hard. I have been doing a developing a wxWidgets based projects for several months before I finally took the time to get the debug build compiled and installed. Although with the intermittent stability issues Code::Blocks (at least on linux) has doing this more often sounds like a good idea. On Monday I will compile the SVN version against wxGTK 2.6 dbg and see what I get.
EDIT: Make that the codeblocks project file, not the project itself.
Michael:
--- Quote from: 280Z28 on January 14, 2006, 07:58:56 pm ---I suggest you post this at the Kirix forums so the author can give feedback on this too. :)
--- End quote ---
I followed your advice and here is the answer from bwilliams:
--- Quote ---Yeah, the code is correct. I suppose the check to make sure the pane exists is a bit padentic, so I'll take care of the problem by removing the unnecessary code.
--- End quote ---
Michael
Navigation
[0] Message Index
[*] Previous page
Go to full version