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

Change the Debugger Toolbar on the fly

<< < (2/4) > >>

scarphin:
Sry for hijacking the topic but a 'reset' button on the debugger toolbar should be implemented somehow for microcontroller work.

oBFusCATed:

--- Quote from: e.p on May 26, 2011, 02:22:56 pm ---We have no "Run to cursor" and no "Information windows".

--- End quote ---
I've plans to make most of the features optional, so in the future a plugin could make the "Run to cursor" menu item disabled or any other such item could be disabled, too.
If you state your requirements I can design the API in a way that it can be fulfilled.


--- Quote from: e.p on May 26, 2011, 02:22:56 pm ---No "Call stack" and no "Threads".

--- End quote ---
"Call stack" and "Threads" windows could be made optional, too, so if plugin doesn't support them, they could be disabled.


--- Quote from: e.p on May 26, 2011, 02:22:56 pm ---In return we have a "Pin Emulation" and a "Debugger Link" window. And a "reset" button.

--- End quote ---
You can add your windows in the debugger plugin, there is no point to modify the core of C::B. The core/sdk should have only the common GUI/features.
If a plugin has something specific it should be implemented inside the plugin.
Also we can rename the "Information windows" to "Auxiliary windows", "Other windows" or something similar.
These are windows created inside the plugin and they could have anything in them.
It looks like these two ("Pin Emulation" and "Debugger Link") are suitable to be implemented as such.


--- Quote from: scarphin on May 26, 2011, 03:58:29 pm ---Sry for hijacking the topic but a 'reset' button on the debugger toolbar should be implemented somehow for microcontroller work.

--- End quote ---
What is the purpose of this button?

Probably it won't be that hard to add API for adding toolbar buttons from inside the debugger plugins. (I should check if this is supported by wxWidgets).
Another option is to make another toolbar, with the buttons you need.

Alatar:

--- Quote from: e.p on May 26, 2011, 01:33:41 pm ---
--- Quote from: oBFusCATed on May 26, 2011, 12:31:53 pm ---Hm, tell us what you want to have in the toolbar and we(I) will see if they could be added/implemented.
--- End quote ---

I don't think it would make sense. The functions are very specific and would be of no use for normal debuggers (it is a hardware debugger).

--- End quote ---

There is many embedder programmers using C::B, so I think it would be useful to have such flexible debugger infrastructure that can support both desktop and UC debugger in same instance of IDE. Same I can say about compiler and project manager frameworks. For example now when I want to add non-standart compiler I must inherit my plugin from cbCompilerPlugin because CompilerGCC developed for traditional compilers, but in this case I can`t reuse many compiler-related code (for example output parser). It would be great to make C::B yet more customizable.

oBFusCATed:

--- Quote from: Alatar on May 26, 2011, 08:47:28 pm ---It would be great to make C::B yet more customizable.

--- End quote ---
Patches welcomed :)

scarphin:

--- Quote from: oBFusCATed on May 26, 2011, 04:21:08 pm ---
--- Quote from: scarphin on May 26, 2011, 03:58:29 pm ---Sry for hijacking the topic but a 'reset' button on the debugger toolbar should be implemented somehow for microcontroller work.

--- End quote ---
What is the purpose of this button?

--- End quote ---

It's basically the same as restarting ur PC. For microcontroller work without a tiny kind of OS running in ur uc it's probable that ur code may crash while running so u need to reset ur hardware. U may do it by hand by switching the power on and off etc... then u have to restart the debugger software (i.e. GDB). Specific debuggers have the option to reset the hardware by software like MPLAB, AVRStudio etc... and they begin debugging from the top of the code. Some 'gdb servers' have certain commands to send a reset signal to the target hardware so this property can be used with gdb. There was a certain command the gdb uses to run a command specific to the 'gdb server' but I can't remember it right now.

Navigation

[0] Message Index

[#] Next page

[*] Previous page