On Tue, May 29, 2012 at 10:09 PM, Flam' <[email protected]> wrote: > Hi, > > I've been waiting for a while for an improved debugger integration as > discussed in the second point of this issue: > http://code.google.com/p/spyderlib/issues/detail?id=554 > > As it appeared a rather simple piece of code, i began to work on it in > a clone i made from spyderlib: > http://code.google.com/r/remiflamary-debugtoolbar/ > > First I added a toolbar with meaningful icons (stolen from matlab for > the moment). > In the corresponding actions, i perform a simple task: > - I raise the external console > - I execute the command corresponding to the debugger action > (next,step,continue,return,exit) > > It appears to be quite usable but there is a problem: toolbar actions > are always enabled (still executes in a python(non-gdb) console with > quite a sad output). > A good idea would be to enable them when a debugger consol is executed > and disable them afterward. But i can't find a way to do that... > > Hope you can use my changes and include them in a next release, a > debugger toolbar his one of the reasons I (and other people i know) > still hesitate to switch fully to matlab. > > Flam'
Can you create slot in the toolbar that sets its Enabled property and connect that to the "destroyed" signal of the debugger console? -Todd -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
