Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Show debugging information on hover
cbexaminr:
Anybody want to give this a try? (windows only tried thus far by me)
Its progressively based on shirsoft's code (hence is just a DEMO, not integrated into codeblocks), and contains a lot of junk that shows or at least hints at the variations I went through to arrive at what's here. Not perfect, but I think better than when I started. Mouse hover over the '+' will open descendants - leaving current will generally close it if it has no descendants. To close cleanly, each descendant must be exited thru its ancestor, or a return to current top then leaving must be repeated for each level. Once the user is trained, it works great ;).
Feature still lacking is some means of adding a scroll bar when the number of items for a given entity "level" won't fit on screen. (Don't know if horizontal scroll might also eventually be needed due to excessive length of any single item.) Since the existing release implementation doesn't seem to allow for such vertical scrolling I don't feel too bad about that yet.
oBFusCATed:
Looks good, no border on E17 which is great :)
There are some bugs:
1. When I hover over + for the sph entry the second level opens, then I hover over the second level and then move my mouse out of both levels, the result is that only the second level is closed.
2. You can show the second level when the first level is closed.
Looking at the code the positions of the windows are calculated in advance, but I think the should be calculated when the level is about to be shown.
Also this control should support scrolling: http://farm1.static.flickr.com/174/416944134_f4d123e9bc_o.png
cbexaminr:
1)Since its apparently too hard to train my users, here's an attempt that may require less training.
2)Do you know what the control is in that image? Is that an image of a wxwidets application? Or were just suggesting that an effort should be made to create a control that resembles that image?
oBFusCATed:
--- Quote from: cbexaminr on August 22, 2010, 08:16:56 pm ---2)Do you know what the control is in that image? Is that an image of a wxwidets application? Or were just suggesting that an effort should be made to create a control that resembles that image?
--- End quote ---
Hm, it seems that you haven't used Visual Studio >=2005.
The screenshot is from their implementation of the Debug hover window and I suppose it is done with win32 api only (another possibility is .net but I doubt).
p.s. will test the new version in a minute...
Edit:
Now it is way better than before, it is closing a bit too fast when the mouse leaves the window, but this should be fixable with some tweaking.
Can you implement the scrolling behaviour?
cbexaminr:
FWIW,
soso news
I have implemented rudimentary scrolling, and I have it integrated into (checkout of) CB wxpropgrid_debugger branch, using the GDBWatch entities. (I didn't actually get scrolling implemented in the demo, because it was going to require too much throw away framework for data structures, since a specific one was going to need to be supported. Hence the move to integration into CB branch.)
bad news
It doesn't work nearly as smoothly integrated into the whole as it seemed to in the much smaller demo program, even after a number of "hacks" attempting to address the various visual, and some not-so-visual, issues I have encountered.
(obfuscated, others) Do you want me to bother attempting to post a patch in its current state. (The code is quite dirty at the moment, as it has my "running history" of the various things I've tried. It only contains code added to gdb_tipwindow.<cpp,h>, (all classes lifted from the demo, not mods to existing tipwindow stuff), and slight change to gdb_commands.h to invoke it. [well, excepting all the update.bat files that are not winxp sp2 compatible, at least in terms of line-endings, that I changed when I originally obtained and built the branch])
I am currently a bit frustrated, but have not yet given up entirely. I'm not sure when that might change, based on available resources and other priorities.
ps - it currently does have borders around the frames, as with default (editor) colors on my winxp mach, it was very hard to see without them. This is currently a minor difference of a flag passed to the underlying frame-descendant constructors.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version