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
Unlike in case of the Classic theme KeePassXC does not underline the access keys (in the menus, in dialog boxes, etc.) while using the Light / Dark themes.
(Note: in Windows turning on "Underline access keys when available" can help w/ the detection.)
Steps to Reproduce
Start application w/ Light/Dark theme.
if "Underline access keys when available" is not turned on, press and release Alt to activate the menubar.
Expected Behavior
Access keys are underlined just as in the case of the Classic theme.
Actual Behavior
Access keys are not underlined.
Context
KeePassXC - Version 2.6.6
Revision: 9c108b9
Qt 5.15.2
Operating system: Windows 10 Version 2009
CPU architecture: x86_64
Kernel: winnt 10.0.19043
The text was updated successfully, but these errors were encountered:
* Fixes#7325
Qt 5.x defaults to always show mnemonic underlines in menus. Qt 6.x fixes this, but we can't port the fix since it relies on private theme namespaces. Anyway, to get around this, simply check if the widget is a menubar and focused. If so, we draw the underlines. Only applies when the user actually presses ALT so this is desired behavior.
NOTE: Underlines in menus will disappear once you focus on the menu, still working on this
Overview
Unlike in case of the Classic theme KeePassXC does not underline the access keys (in the menus, in dialog boxes, etc.) while using the Light / Dark themes.
(Note: in Windows turning on "Underline access keys when available" can help w/ the detection.)
Steps to Reproduce
Alt
to activate the menubar.Expected Behavior
Access keys are underlined just as in the case of the Classic theme.
Actual Behavior
Access keys are not underlined.
Context
KeePassXC - Version 2.6.6
Revision: 9c108b9
Qt 5.15.2
Operating system: Windows 10 Version 2009
CPU architecture: x86_64
Kernel: winnt 10.0.19043
The text was updated successfully, but these errors were encountered: