octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49571] Command-c and command-v aren't default


From: John Swensen
Subject: [Octave-bug-tracker] [bug #49571] Command-c and command-v aren't default cut/paste in editor (and command-v doesn't work even when changed in preferences)
Date: Thu, 10 Nov 2016 17:48:36 +0000 (UTC)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.44 Safari/537.36

Follow-up Comment #7, bug #49571 (project octave):

Sorry to comment so much, but I just did a quick test of removing all the
Q_OS_MAC specific sections of the UI code that related to keyboard shortcuts
and everything work exactly as I expect it to, with one exception. The
exception is that in the terminal window, now command-c is what is necessary
to interrupt the execution of a script. This kindof makes sense because QT5
tries to make command-c do what control-c would be on any other platform.

This seems to indicate to me that there have been improvements to both
QScintilla and QT5 that allows software to be written once and have the
shortcut behavior be OS-consistent with other apps, but without having to
change anything.

So, my proposed patch would include the following:
1) remove all the existing Q_OS_MAC related shortcut code to allow QT5 and
QScintilla to do the OS-specific mapping on its own.
2) Add new Q_OS_MAC related shortcut code to the command window to make ctrl-c
be interrupt and command-c be copy.
3) Add new Q_OS_MAC related code to use the right language in the preferences
pane for command, option, and control modifiers.

Thoughts?


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]