Hmm, because I have to display data structures? :? What other way is possible to display them? Or what is it wrong specifically?
Every plugin can implement this methods (
AddVisualObject and
DeleteVisualObject), and then create your own visual representation of watch. This representation will be created then by calling this method.
My idea was, that every plugin can implement your own representation of watch, which will be displayed on the canvas. My representation is tree control, but some other plugin can implement it other way.
This is great idea. I can try it
But what is major problem then?
ad p.s. I tried to do things similar to nearest code. I read articles about formatting and other advices in C::B, but I saw that every piece of code has his own formatting and logic. I write GUI in
xrc instead of
wxs because all other windows was written in this format. This is what you point to? I can read about wxSmith, but I don't know where should I use it.
ad p.p.s. I was also thinking this way, but I followed by your advise:
m.29:
Probably you need to modify the sdk and put most of the drawing code and data structures there.
If you do so all plugins can implement this graphical mode, not only the current one and there will be minimal code duplication.
See how it is done for the other features (watches, breakpoints, etc).
I look at how it is done for watches and then create similar
cbVisualObject. I tried implement it as a separate plugin, but I don't know how, because I want to add functionality to
GDBDebugger and I haven't access to its structures (e.g.:
GDBWatch) in separate plugin.