[Octave-bug-tracker] [bug #50295] Calling feval() from within the Qt GUI requires to press enter otherwise the prompt is busy

[John W. Eaton]

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

I think the behavior you are seeing is expected.  When you write to the
command window, Octave doesn't redraw the prompt after your output.  Is the
behavior the same for you with the following code?


function foo ()
  disp ('foo!');
endfunction
h = figure ();
set (h, 'buttondownfcn', @foo);
## Now, "foo!" should appear in the command
## window each time there is a mouse click
## in the figure window.


Maybe Octave should redraw the prompt, but I'm not sure exactly when that
should happen or what should trigger it.  I know, you are probably thinking
"after output is displayed in the command window", but how much output?  After
each callback function is executed, or just after a series of them have been
executed and there are no more pending events?  How do we know there won't be
more events arriving?

    _______________________________________________________

Reply to this item at:

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

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