Xpra: Ticket #945: OSX Launcher has wrong keymapping
This a trivial issue....but will need to be fixed to meet OSX's (annoying) style quidelines/user expectations.
Tested with the latest (as of 2015-8-12) OSX beta build r10258 from /beta:
- Typing information into the address for a TCP connection and pressing
CMD + A does not select all text. Instead the user must press
Ctrl + A, which does not match OSX user expectations.
Thu, 13 Aug 2015 02:49:57 GMT - Antoine Martin: priority, status, milestone changed
changed from minor to trivial
changed from new to assigned
changed from 0.16 to future
This a toolkit issue (gtk-osx), not one we should try to workaround ourselves.
And I doubt that gtk will patch things... so delaying this ticket.
Sun, 19 Feb 2017 07:10:54 GMT - Antoine Martin: status changed; resolution set
changed from assigned to closed
set to wontfix
Could be looked at with #1343
Found some links:
- inkskape: Keyboard shortcuts are not mapped to command key
- GTK+ OSX Integration: The automatic conversion of control-foo menu accelerators to command-foo has not been carried over to GtkOSXApplication, though a new facility is provided in Gtk+ (as of this writing it is in Git for Gtk+-2.24, and released in Gtk+-3.2.0) to use the <Primary> descriptor in place of <Control> for accelerators and bindings. This will map the accelerator to Command on OSX and to Control for anything else.
But unfortunately, that's not the case for widgets and the widget object doesn't have methods for reading the current accelerators, so we can't patch them on the fly.
Sat, 23 Jan 2021 05:10:31 GMT - migration script:
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/945