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

[Lachlan Andrew]

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

Dan, I agree entirely with your first sentence in comment #7.

If you have clear idea of what the "proper framework conventions" should be,
please document them.  I'll be happy to try to work within it, even if it is
by writing kludge shims to be replaced when the proper framework is developed
as you suggest.  I just have don't really know what the framework should look
like.  For this particular bug, I'll have a go at what you suggested, but it
would be nice to have something more general written down.

Arguing about whether or not a cross-thread fix makes the code "less buggy" is
a bit like arguing whether or not Lewis Carol was right that a clock with
stationary hands is "better" than one that looses one minute per day.  (The
one with stationary hands is exactly right twice a day, which is much more
often than the other one is right, but the one with moving hands is more
useful.)



The structure returned by all functions is an octave_value_list.  I'm not
convinced that the best approach is simply to allow CLI commands to be run by
the GUI.  It would be useful to have a more generic thread-safe way to make a
core function callable from the GUI. You have pointed out that this is harder
to debug than the more restrictive CLI-like interface.  There's always a
tradeoff, with multiple useful combinations.

    _______________________________________________________

Reply to this item at:

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

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