octave-maintainers
[Top][All Lists]
Advanced

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

Re: Connecting Octave to the GUI


From: John W. Eaton
Subject: Re: Connecting Octave to the GUI
Date: Thu, 04 Apr 2013 00:30:14 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11

On 04/04/2013 12:13 AM, Daniel J Sebald wrote:

Another thing that will need to be done is to disallow editing of the
file when in debug mode. Right now, accidentally typing return in the
editor instead of terminal window will edit the file. Yellow arrows
start showing up all over the place at lines that keep changing. What
should happen is if the user types in the editor window when in debug
mode, a question dialog should pop up asking "Would you like to leave
debug mode?". If the file changes, how should breakpoints be readjusted?
Lots of coordination to do here still.

Making changes to the file only causes trouble for the debugger if
the file is saved and must be parsed again because the timestamp on
the file changes.  Breakpoints are currently stored in the parse tree,
so parsing the file again will delete all the previous breakpoints.
It doesn't make much sense to me to save and restore them if the file has
changed since there is no reason to expect that the file has the same
contents.

I understand that that with the display of breakpoint and current
debugger position information that there are some problems that are
unique to the GUI, but the problem of breakpoints being cleared is
not, because there is nothing that prevents editing a file while you
are also debugging it with the command-line version of Octave.
Similarly, if we lock the file in the GUI editor, there is nothing to
prevent you from editing the file with some other editor while the GUI
is running.

jwe


reply via email to

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