[Octave-bug-tracker] [bug #44485] GUI: File | Exit from main menu doesn't work when Octave is busy

[Philip Nienhuis]

Follow-up Comment #14, bug #44485 (project octave):

OK got some results.

You patch didn't apply cleanly; one reject hd to be accomodated in a block, so
that may be a reason for the half-baked results I get below.

On both Linux and Windows, it worked the first time:
for ii=1:100;
a = eigs (rand (500));
endfor
could be interrupted by the main menu's File|Exit. Took a second, then I got a
popup.

The interrupt may be too "hard" and looks like a system call to kill a
non-behaving program, on Windows I also get the "program crashed" popup.

However, subsequent attempts fail (maybe because of me wrongly fitting in the
reject).
When I have a file in the editor with -non-saved changes, nothing happens
either (but that was the second attempt, maybe it has nothing to do with the
editor).

Am I right that that a system call is invoked?
If so think it would be preferrable if Octave's current occupation is
interrupted, and then Octave exits gracefully through its own mechanism rather
than rely on the system interrupt.


    _______________________________________________________

Reply to this item at:

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

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