Re: Debugging and the GUI Editor; Qt help needed

[Daniel J Sebald]

On 03/28/2013 02: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.

Let me toss out an idea, just to give an alternate paradigm on this. 
There are other ways to do this, I imagine.  Say I want to run the 
"dbstop" command at the command line and that causes a red (yellow?) dot 
to appear next to the appropriate line in the editor.  And I want to do 
so without any alteration to the core Octave code.  I might do the 
following:

1) Write a builtin routine "qtdbstop(FILE,RLINE)" that will send a 
signal to the editor that it should place a dot somewhere.

2) Now, create an M-script (kept under the libgui code) that will 
override Octave's dbstop internal routine, something like:

function
  try
    RLINE = dbstop (FUNC,LINE);
    qtdbstop (FILE,RLINE);
  catch
    display ("Sorry, break point not set");
  endtry

Is it possible to call Octave's builtin function from within an M-script 
with the same name?

Dan