[Octave-bug-tracker] [bug #47585] GUI editor does not show already active breakpoints when a file is opened

[Dan Sebald]

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

I pointed out several years ago that this would be a problem because the
callback functions for breakpoints and such is driven from the core side of
things and the core does not know the editor has opened a file.  The only
thing really needed for all sorts of functionality is a way to send commands
to the core and eventually get an octave_value_list return value for that
processed command.  In this case, the editor would initiate a "dbstop" and
when the signal (not a function call, but a signal) comes back from that
processed command with the list of breakpoints in an octave_value_list then
the editor would add the breakpoints.  See

https://savannah.gnu.org/patch/?func=detailitem&item_id=8016#options


    _______________________________________________________

Reply to this item at:

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

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