Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
I use the default font at the moment. The font in the editor has other requirements (monospace-ness).
OK, I would implement the same GUI as the editor's font settings.
ollydbg:
Patch v2(still against rev 7366), though I have done every thing to emulate a cb event, it seems I still failed to show the debugger's tip when ctrl pressed. hope some one can help, thanks.
dmoore:
Hi Guys! Long time no post.
--- Quote from: oBFusCATed on August 12, 2011, 03:23:57 pm ---No, I won't add two settings! There are plenty of options in the config dialogs already.
--- End quote ---
Off Topic: Agree that its cluttered, but that's a reflection of a bad UI for settings, not too many settings. I think we need some mechanism for changing advanced settings that doesn't involve hand editing xml, such as a searchable property sheet, so that we can give new users simpler settings dialogs and advanced users more flexibility.
On Topic: I should probably just read the thread/code, but do you have a cliff notes version of the status of your work on the debugger API, oBFus? (May have some free time to think about the python debugger again in coming months)
oBFusCATed:
dmoore: Probably you're right that something like "about:config" will be very handy.... :)
Regarding the API, I plan to replace all the raw pointers with cb::shared_ptr (where applicable of course) and then I'll focus on the gdb_mi plugin for a while...
ollydbg:
--- Quote from: ollydbg on August 12, 2011, 04:29:32 pm ---Patch v2(still against rev 7366), though I have done every thing to emulate a cb event, it seems I still failed to show the debugger's tip when ctrl pressed. hope some one can help, thanks.
--- End quote ---
Ok, I solved the problems in v2 patch, and now when I hit the ctrl key, the debugger will show the tip now. (test only under WinXP). the reason v2 failed is that I forget setting the editor pointer in the emulated c::b event.
see the v3 patch (which is against debugger_branch rev 7376), note I have some DebugLog function in the patch, you can safely remove them. I admit that the emulated way is not quite good, it looks like a hack. :D
comments are welcome!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version