Re: Debugging and the GUI Editor; Qt help needed

[John W. Eaton]

On 03/28/2013 03:18 PM, Daniel J Sebald wrote:
> On 03/28/2013 02:00 PM, Daniel J Sebald wrote:
>
> > Think in terms like this:
> >
> > |
> > OCTAVE CORE <--> BUILTIN COMM OBJECT | GUI THREAD
> > |
>
> I should point out that the item labeled "BUILTIN COMM OBJECT" is not
> included if the GUI is not compiled as part of octave. That is why I've
> put the builtin routines I've written under "libgui" and not "libinterp"
> where all the other builtin functions are.

I'm still not sure I understand, but let me try to explain what
currently happens when using dbstop at the Octave command window
prompt as that is I think similar to your dialog example.

Initially, a callback function is installed when the
GUI starts so that the GUI can take some action when a breakpoint is
inserted in the Octave interpreter's table of breakpoints.

So, when dbstop is called, Octave sets the breakpoint in the
interpreter and calls the function installed by the GUI.

That function extracts the file and line number information and
ultimately calls octave_qt_event_listener::update_dbstop_marker, which
emits the signal update_dbstop_marker_signal.  That signal is handled by
main_window::handle_update_dbstop_marker_request, which calls
functions from the file_editor class to display the breakpoint marker
icon in the GUI edidtor window.

Which of these function calls is not safe to perform, or called in the
wrong context?

How should this job be done differently?

jwe