[Octave-patch-tracker] [patch #8006] New marker class to maintain breakpoints and position in modified files

[Dan Sebald]

Follow-up Comment #2, patch #8006 (project octave):

Yes, the fprintf are only temporary things.  (I use them because then it is
easy to search and remove.)  In this case they are just meant to point out it
is in fact the core debugger that is creating the placing the debug marker in
the subfunction rather than some bad GUI code.  Hard to tell sometimes. 
(Hopefully that is fixed with the changeset you pointed out.)

Oddly enough, I couldn't figure out how to include the PNG files in the
changeset.  The files were added to the mercurial project without problems.

OK, copyright I was never sure of how that works.

The UI file change was done with a nice utility called designer-qt4 on my
system.  Use "designer-qt4 settings-dialog.ui &" at the command line.  It's
all pretty self explanatory.  Clicking on an item in Object Inspector,
QTabWidget, Signal/Slot brings up properties, etc.  Can select, copy and edit
objects on the layout and changes will show up in the windows Object
Inspector, etc.  This utility would be nice for more advanced features, but
for the smaller things like the errordlg, questdlg, it is just as easy to
construct those using a few lines of code.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8006>

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