Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Auto-layout switching for debugger

(1/3) > >>

mandrav:
I implemented what the title says.
It's cool to see it in action but an initial manual configuration must be done by the user.
So here I will describe the two steps you have to take to make it work.

What has been added, is two text boxes in "Settings->Debugger" where you can type the names of two layouts:
1) The layout to switch to when the debugging session starts
2) The layout to switch to when the debugging session ends

If one of these is empty (the default), no layout switching takes place in the respective session point (start/end).
So, how do we glue these together? Fear not. It only takes two steps :)

[*] If you haven't done so already, create a layout for debugging. I.e. open the watches window, put it where you want, open the callstack, put it where you want, etc. You get the point. Open any windows you like and arrange them as you like. When you 're happy, click "View->Layouts->Save current". Name it as you like (I suggest "Debugging" :P).
[*] Go to "Settings->Debugger". Type in the first layout box (debugging start) the name of the layout you saved, e.g. "Debugging" (no quotes). Then type in the second layout box (debugging end) "Code::Blocks default" (or any other you might have created).
[/list]

Now start a debugging session and enjoy :)

Michael:

--- Quote from: mandrav on January 11, 2006, 02:06:12 pm ---I implemented what the title says.
It's cool to see it in action but an initial manual configuration must be done by the user.
So here I will describe the two steps you have to take to make it work.

What has been added, is two text boxes in "Settings->Debugger" where you can type the names of two layouts:
1) The layout to switch to when the debugging session starts
2) The layout to switch to when the debugging session ends

If one of these is empty (the default), no layout switching takes place in the respective session point (start/end).
So, how do we glue these together? Fear not. It only takes two steps :)

[*] If you haven't done so already, create a layout for debugging. I.e. open the watches window, put it where you want, open the callstack, put it where you want, etc. You get the point. Open any windows you like and arrange them as you like. When you 're happy, click "View->Layouts->Save current". Name it as you like (I suggest "Debugging" :P).
[*] Go to "Settings->Debugger". Type in the first layout box (debugging start) the name of the layout you saved, e.g. "Debugging" (no quotes). Then type in the second layout box (debugging end) "Code::Blocks default" (or any other you might have created).
[/list]

Now start a debugging session and enjoy :)

--- End quote ---

This is a useful addition IMHO :D. It is "similar" as in Visual Studio .NET (and I think, but not sure, Eclipse), when you start a debug session, correct?

Michael

280Z28:
Can you make it:

When the debugger starts, the current layout is stored (anonymous, direct call to wxFrameManager to get the layout).

When the debugger stops, the current layout is stored in the layout file or wherever C::B stores layout info, in a branch just for the debugger. Then the layout that it remembered from the debugger starting is restored.

?

thomas:

--- Quote from: 280Z28 on January 11, 2006, 04:57:35 pm ---Can you make it:
--- End quote ---
Why? The event based approach is a lot better, as it is truly universal.

280Z28:

--- Quote from: thomas on January 11, 2006, 05:05:46 pm ---
--- Quote from: 280Z28 on January 11, 2006, 04:57:35 pm ---Can you make it:
--- End quote ---
Why? The event based approach is a lot better, as it is truly universal.

--- End quote ---

Huh? We must not be talking about the same thing.  :?

Navigation

[0] Message Index

[#] Next page