[Octave-bug-tracker] [bug #39723] history commands lost when selecting block and right-clicking "Evaluate"

[Dan Sebald]

Follow-up Comment #4, bug #39723 (project octave):

I've already done such a thing here:

https://savannah.gnu.org/patch/?8016

so before getting too far and reinventing the wheel, you might want to check
that out.  (Or not, to see if what you come up with is different.)

The queuing features are in the functions:


void
octave_qt_link::do_process_events (void)



void
octave_qt_link::handle_queue_octave_command (const QString& command,
                                             const int nargout)


The additional feature in the above link is a way to send the result of the
command back to the GUI but isn't essential for queuing, but instead avoiding
callbacks:


void
octave_qt_link::receive_octave_command_result (const QObject *ID,
                                               const QString& command,
                                               const int status,
                                               const octave_value_list&
output)



void
octave_qt_link::receive_octave_command_result (const QObject *ID,
                                               const QString& command,
                                               const int status,
                                               const octave_value_list&
output)


The reason I suggest just going with what you have is that it is small change.
 We've had plenty of discussion on the list about a robust simple way of
communicating between worker and GUI.  I don't see the point of having a
robust queuing system and callbacks and whatever else might be in the software
right now.

    _______________________________________________________

Reply to this item at:

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

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