#945 closed defect (wontfix)
OSX Launcher has wrong keymapping
Reported by: | J. Max Mena | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | trivial | Milestone: | future |
Component: | client | Version: | trunk |
Keywords: | Cc: |
Description
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 pressCtrl + A
, which does not match OSX user expectations.
Change History (3)
comment:1 Changed 6 years ago by
Milestone: | 0.16 → future |
---|---|
Priority: | minor → trivial |
Status: | new → assigned |
comment:2 Changed 4 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
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.
comment:3 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/945
Note: See
TracTickets for help on using
tickets.
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.