https://bugs.kde.org/show_bug.cgi?id=483640
Cajus Pollmeier <k...@cajus.naasa.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@cajus.naasa.net
--- Comment #1 from Cajus Pollmeier <k...@cajus.naasa.net> ---
According to the KDE xdg portal source, the name registered there is the appId
+ the last part of the session object path. Hmm.
If you have a flatpak with the appID org.foo.bar and create some key bindings
with it, your app ends up as "org.foo.barSOMENUMBER" in the key bindings KCM.
Firstly - from the end user perspective, I'd expect to see the real name of the
flatpak there, no technical id + session path.
Secondly - this leads to the problem that you can't persist the keyboard
bindings, because every time you start the App (i.e. after a reboot), you'll
end up with a new session ID, and while your old settings still "pollute" the
KCM keyboard settings, the newly registered create conflicts (or even do not
reflect what you've set up before).
How is this supposed to work? Could anyone of the KDE devs shed some light on
how to use this interface properly? Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
