Show keyboard shortcut in right-click menu too
Submitted by an unknown user
Link to original bug (#717069)
Description
---- Reported by shotwell-maint@gnome.bugs 2010-11-08 09:18:00 -0800 ----
Original Redmine bug id: 2777
Original URL: http://redmine.yorba.org/issues/2777
Searchable id: yorba-bug-2777
Original author: Jules Kerssemakers
Original description:
Currently, keyboard shortcuts for actions are displayed in the main program menus (e.g. “Tags†> “Add Tags Ctrl+Tâ€), but the same actions in the right-click menu do not show the keyboard shortcuts.
This seems inconsistent to me. I would expect that identical actions are labeled identically in different menu's.
This also provides right-clicking users with the same hints as those using the main program menu (which I believe is less-used generally)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:46:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 3 years ago
- Status changed from Open to 5
- Resolution set to wontfix
- % Done set to 0
Shotwell is designed to have a consistent look and feel with the rest of the GNOME desktop. Other GNOME applications don't display keyboard shortcuts in context menus, and so Shotwell won't either. Marking as wontfix.
If you think GNOME applications should display keyboard shortcuts in context menus in general, you could suggest that to the GTK team.
Comment 2
Updated by Jules Kerssemakers about 3 years ago
oh, oops. Excellent reason, I've honestly never noticed that before though.. Sorry to bother you then :-)
Comment 3
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:48 UTC ---
This bug was previously known as bug 2777 at http://redmine.yorba.org/show_bug.cgi?id=2777
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID