You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Qt 5.10, shortcuts are no longer shown by default in context menus. However, I'd generally prefer them to be there to make them discoverable. Several actions that are only available from context menus have shortcuts that are now completely hidden.
It seems the only way to fix this is to manually specify that the shortcut should be visible for each affected action. Setting setAttribute(Qt::AA_DontShowShortcutsInContextMenus, false) has no effect, since QAction is doing:
@mitchcurtis Ah, thanks for the reference! It didn't occur to me to look for an issue because the change in behavior was clearly intensional, but I think it is a little misguided and I hope they will reconsider, or at least provide an API for enabling the showing of shortcuts in all context menus.
Unfortunately this issue persists in Qt 5.11 and Qt 5.12 (LTS). This means for now I'm going to stick to releasing against Qt 5.9, which may be a better choice in regards to stability anyway.
Since Qt 5.13.1, shortcuts are again visible by default in context menus, except on macOS, where they are deemed too out-of-place. I'll make it so that they're always shown when the "Tiled Fusion" style is selected, which is now possible using QGuiApplication::styleHints()->setShowShortcutsInContextMenus(true).
In Qt 5.10, shortcuts are no longer shown by default in context menus. However, I'd generally prefer them to be there to make them discoverable. Several actions that are only available from context menus have shortcuts that are now completely hidden.
It seems the only way to fix this is to manually specify that the shortcut should be visible for each affected action. Setting
setAttribute(Qt::AA_DontShowShortcutsInContextMenus, false)
has no effect, sinceQAction
is doing:And the style hints say they should not be visible.
The text was updated successfully, but these errors were encountered: