https://bugs.kde.org/show_bug.cgi?id=518683
--- Comment #5 from Noah Davis <[email protected]> --- Since you seem technically inclined, here is how the key sequence for `QKeySequence::HelpContents` is defined, in order: 1. Spectacle gets the key sequence from our Qt platform theme plugin. - https://invent.kde.org/plasma/plasma-integration/-/blob/master/qt6/src/platformtheme/kdeplatformtheme.cpp?ref_type=heads#L185 2. Our platform theme gets the key sequence from KStandardShortcut, which gets the key sequence from either its own internal `initialize()` function where it searches for `Help` in the `[Shortcuts]` section of `~/.config/kdeglobals` or its own default shortcuts (`Qt::Key_F1` in this case). - https://invent.kde.org/frameworks/kconfig/-/blob/master/src/gui/kstandardshortcut.cpp?ref_type=heads#L320 - https://invent.kde.org/frameworks/kconfig/-/blob/master/src/gui/kstandardshortcut.cpp?ref_type=heads#L551 That's where it ends for `QKeySequence::HelpContents`, so the cause of your issue is unlikely to be in Spectacle. Standard QKeySequence shortcuts that don't have custom definitions coming from our platform theme get their definitions through the base QPlatformTheme class, but `QKeySequence::HelpContents` has a custom definition. - https://codebrowser.dev/qt6/qtbase/src/gui/kernel/qplatformtheme.cpp.html#187 (see shortcuts with KB_KDE, KB_X11 or KB_All) -- You are receiving this mail because: You are watching all bug changes.
