octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #47585] GUI editor does not show already activ


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #47585] GUI editor does not show already active breakpoints when a file is opened
Date: Mon, 04 Apr 2016 02:19:14 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0

Follow-up Comment #3, bug #47585 (project octave):

Yes, related, but only in the sense that there needs to be communication in
both directions across the GUI "boundary", be it a thread or some other
configuration.  I put together a detailed description at one point,
classifying the various actions in the whole framework.

When it is the GUI side initiating action, there is a wealth of commands for
getting breakpoints, getting variables, setting variables, getting properties,
setting properties, etc.  All these can be accessed via some command/return I
described in a previous post.

Then there is the case where an action is initiated in the core--or maybe I
should say initiated from the command line via the core.  What's a nice way of
handling that?  A way that doesn't require writing all kinds of GUI-specific
code in the core?  A way that any number of GUI frameworks could make use of? 
I propose a means to "override" the command-line function very similar to the
way C++ derived classes can override the base class function (and still call
that function if necessary).  I would imagine that almost exists already
because we can create our own functions having the same name as some existing
function in Octave.  The thing that is missing is the ability to still call
the built-in functions somehow.

The GUI when launched would install its own set of functions that need to
cause some kind of GUI action from the command line.  As an example:

INSTALLABLE_FUNCTION_CLASS(dbclear) qt_gui_dbclear(void)
{
  BASE_FUNCTION(dbclear);
  send_signal_to_GUI_to_update_breakpoints();
}

Something like that.  GUI frameworks other than Qt could make use of this very
generic layout in the same way.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47585>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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