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

[Dan Sebald]

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

I wouldn't call what I'm proposing "niceties"; more like a design principle.

The designers of Qt came up with the signals and slots concept because they
often found the callback routine approach to be limiting and sometimes became
a bottleneck.  There is discussion about this on the web if one does a search
for Qt and callbacks.

I can understand the desire for making the breakpoints work, but I wouldn't
advocate this patch.  One has to keep in mind that the GUI is running in a
different thread and calling core routines asynchronous with what the core may
be doing requires some type of semaphore or mutex.  Otherwise, there is a the
remote possibility of the core changing something, in this case, in the
breakpoint table, at the same time the GUI is trying to access it.  And these
types of obscure bugs are really difficult to locate because they are near
impossible to reproduce when someone reports a problem.

I see a lot of quick-fix, workarounds that push a problem into some other
corner but never completely solve the problem in graphics, breakpoints, dialog
boxes, etc.  If all that effort had been put into a good design principle
early on, it would have been more productive.

    _______________________________________________________

Reply to this item at:

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

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