Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
MortenMacFly:
--- Quote from: Pecan on November 14, 2011, 04:21:39 pm ---
--- Code: --- // compiler set buttons
if (XRCCTRL(*this, "btnAddCompiler", wxButton)) // only if exist
{
en = !data; // global options selected
--- End code ---
--- End quote ---
I saw that, too already. IMHO the old code was a hack to differ between the dialog with the global compiler options and the dialog local (project/target based) options. This was implemented rather bad, obviously... ;-)
EDIT: My intention was to directly check for a valid m_pProject pointer, which means, a project is present (not valid for the global compiler dialog). It doesn't seem to work though... :-(
Jenna:
The compileroptionsdialog is used in two places:
one time as panel from "Settings -> Compiler and debugger" (compilergcc.cpp:548), without a project,
and the other time if "Project -> Build options" is clicked (compilergcc.cpp:526), with a project of course.
So different controls are needed and therefore shown.
Jenna:
--- Quote from: MortenMacFly on November 14, 2011, 04:40:02 pm ---
--- Quote from: Pecan on November 14, 2011, 04:21:39 pm ---
--- Code: --- // compiler set buttons
if (XRCCTRL(*this, "btnAddCompiler", wxButton)) // only if exist
{
en = !data; // global options selected
--- End code ---
--- End quote ---
I saw that, too already. IMHO the old code was a hack to differ between the dialog with the global compiler options and the dialog local (project/target based) options. This was implemented rather bad, obviously... ;-)
EDIT: My intention was to directly check for a valid m_pProject pointer, which means, a project is present (not valid for the global compiler dialog). It doesn't seem to work though... :-(
--- End quote ---
It seems to works correctly here.
MortenMacFly:
--- Quote from: jens on November 14, 2011, 09:28:35 pm ---EDIT: My intention was to directly check for a valid m_pProject pointer, which means, a project is present (not valid for the global compiler dialog). It doesn't seem to work though... :-(
[...]
It seems to works correctly here.
--- End quote ---
That would be good news... I can't try myself atm...
MortenMacFly:
I assume the latest changes in the debugger branch broke the batch build feature of C::B. The effect is strange: The wxScintilla control cannot be created and C::B crashes.
The crash log points to:
DebuggerManager -> SetInterfaceFactory -> cbDebugInterfaceFactory
To reproduce, try to run a batch build like this:
codeblocks --batch-build-notify --no-batch-window-close --target=All --build WhatEver.workspace
Does it happen for you, too?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version