Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
Thanks, I'll test as I get home.
sbezgodov:
--- Quote from: oBFusCATed on March 18, 2010, 02:14:03 pm ---No sure what you're talking about, can you explain better?
--- End quote ---
Debugger has commands. Would be great if Start and Continue commands has same keyboard key, e.g. F5 and menu entry.
Example: I start debugging by pressing F5 (now F8). My program reaches breakpoint. Then again press F5 (now Ctrl-F7) and my program continues.
Keybinder plugin doesn't allow to bind two commands to one key.
oBFusCATed:
Morten: Can you do another wxPropGrid update? :lol: 8)
MortenMacFly:
--- Quote from: oBFusCATed on March 26, 2010, 12:31:12 pm ---Morten: Can you do another wxPropGrid update? :lol: 8)
--- End quote ---
What about setting up an automatic email that reminds me every week or so?! :lol:
Seriously: It'll need some time, I am without an up-to-date C::B at the moment... so it'll have to wait until Monday, most likely.
Let me take the answer to tell you that the new framework still works just fine for me. I was debugging quite a lot recently (including th new "pause" button ;-)). No issues so far.... anything I should try explicitly next time?
oBFusCATed:
uf, I've missed this last post :(
There were some linux specific bugs in wxPropGrid.
What you should look for:
1. Rendering/refreshing bugs in the watches window when:
* opening/closing a watch
* deleting watch with the context menu and keyboard (delete key)
* renaming a watch with the context menu and keyboard (insert key)
2. Does highlighting the changes when stepping through the code works correctly.
I'll post a patch that has some small fixes in the watches window...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version