Unexpected UI behavior : debugging a tk UI incorporates DDT UI in the tk UI

[stanpetit]

Dear Andreas.
I couldn't manage to use RamDebug on a UI stuff and your project is saving my days ! It works great, congratulation !

The ddt_debugger (DDT) UI has a strange behavior : when running an opened file, lets call it app, the DDT's UI incorporates itself into the app's window, creating it's own splitted paned window on the north side of the main window. It does this quite "gently", without any apparent side effect on the app's UI reactivity.

But from the moment when the app's UI is loaded, DDT's UI looses it's own menus, window title ... no way to open another file from the menu !

The app is the Drakon Editor, full tcl, that I intend to modify a bit : some aspects of the UI are cumbersome to use, mostly the search-replace tool (almost finished) and the navigation though the diagrams hierarchy (todo, much work) ... I like this tool and try to make it more comfortable.

Could you give some hints to manage this, as it remains quite tricky : if I understand, an image of the file to debug is launched in DDT's own's process, hence DDT's own's window ... that soon gets overridden by the app's window properties ...

In my thoughts, I would try to modify ddt.tcl with a case on which the creation of an app's UI would create another (slave) process to host it ... but would DDT still handle the source ? I can't figure it out !
Or should I add a popup menu on the code window of DDT, pointing to the file_menu commands ?

Thank you for DDT, simple, works great !
Best, Stanislas

[Drolla]

Hi Stanislas,
I am wondering if you are looking for the following feature that is in fact already supported by DDT:
DDT can debug a script or application either in the interpreter used by DDT itself (main interpreter), or it can debug it in a separate interpreter that is dedicated to the script/application to debug (slave interpreter). By selecting a separate slave interpreter for your application, the debugger (DDT) and your application will be properly separated from a UI perspective.

To select a separate slave interpreter for your application, run the following DDT command:

ddt::Config -UseSI 1

Or if you are running the graphical DDT debugger (ddt_debugger.tcl), you can select in the Config menu "Use slave interpreter".

Let me know if this works for you.

I just recognize that the documentation about the different configuration options is not well generated! I will make sure that the documentation (wiki) will be updated!

Best regards,
Andreas