[Octave-bug-tracker] [bug #44397] Non functioning Ctrl-C copy/interrupt

[Rik]

Update of bug #44397 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #6:

There is obviously something going on.

Test results:

Linux:
  1) Break between system calls : WORKS
  2) Break in Octave code       : WORKS

Windows:
  1) Break between system calls : FAILS
  2) Break in Octave code       : FAILS


According to Windows "start' documentation


/b : Starts an application without opening a new Command Prompt window. CTRL+C
handling is ignored unless the application enables CTRL+C processing. Use
CTRL+BREAK to interrupt the application.


If I change octave.bat to eliminate the '/B' switch then Ctrl+C goes back to
working.  Also, If I use the vbs script, the Ctrl+C processing works.  The
problem, as reported on the bug report about cmd windows, is that the vbs
script fails to show the window if the Config Wizard needs to be run.

It seems like we need to figure out how to call the Raise Window function in
Qt before the Config Wizard.


    _______________________________________________________

Reply to this item at:

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

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