How does that clashes with a mostly API less KGlobalAccel?
Would allow removing the dep on KGlobalAccel, and also see https://phabricator.kde.org/T12122
How does that clashes with a mostly API less KGlobalAccel?
Would allow removing the dep on KGlobalAccel, and also see https://phabricator.kde.org/T12122
Status | Assigned | Task | ||
---|---|---|---|---|
Open | None | T11536 KDeclarative breakup plan | ||
Open | None | T12125 Move KeySequenceItem to KGlobalAccel -> Became KeySequenceRecorder in KGuiAddons |
For now I would like to start by moving the recording logic to KGlobalAccel so we don't have two copies and subtle differences between both and bugs because of that because one gets fixed and the doesn't.
So KXmlGui supports being build without KGlobalAccel. The only dependecy I need from other frameworks right now is KKeyServer::isShiftAsModifierAllowed which is a big switch. If I copy that, it can even be put into KGuiAddons. There could be other ways to achieve the same but for let's do a 1:1 transfer of the logic.
Not yet I think. We still need a new place for KeySequenceItem and not sure if we are happy with KKeySequenceWidget in XmlGui. Currently both do conflict checking and need KGlobalAccel and KConfig(Gui) for that. On top of that they show message boxes so also Widgets