octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging and the GUI Editor; Qt help needed


From: John W. Eaton
Subject: Re: Debugging and the GUI Editor; Qt help needed
Date: Thu, 28 Mar 2013 10:44:10 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11

On 03/28/2013 07:44 AM, Torsten wrote:
On 28.03.2013 08:43, John W. Eaton wrote:

The cursor is often displayed at the bottom of the window.  It might be
nice to automatically recenter.  Does someone know how to do that with
QScintilla?  I looked, but couldn't see how to do it easily.

Changeset http://hg.savannah.gnu.org/hgweb/octave/rev/f3c93e387865
should fix this.

Thanks. Should we also scroll the window to keep the position marker (the yellow arrow) near the center?

If the command and editor widgets are tabbed or if the editor widget is
floating and overlapping with the main window it is not possible to have
both visible. Should the command widget keep the focus when the
breakpoint was set from the command line?

What should be done if the debugger stops at a breakpoint? I suggest to
bring the editor on top.

If both editor and command window are tabbed, is it possible to split the area where the editor and command window tabs appear so that one is above the other? If either is detached, then I think it is fine to leave them alone as presumably the user has arranged them in some way.

The directory in octave has to be set to the one of the script opened in
the editor if the breakpoints are set in the editor. Maybe this can be
done by just setting the directory before calling dpstop.

I think this problem is not limited to the GUI. The debugger is currently limited to setting breakpoints using only a function name. The file found then depends in some way on the symbol table. It should probably be possible to set a breakpoint in a file directly.

The debugger marker (yellow arrow) is not deleted when the script is
continued.

When continuing from the editor menu (or the toolbar) the script is not
continued before I hit return at the debug>  prompt. This bug already
existed before and is not related to your changes (s. bug #38319).

OK, I'll check these out.

Thanks,

jwe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]