Summary: | Custom application shortcuts set via kmenuedit don't work and are not remembered | ||
---|---|---|---|
Product: | [Unmaintained] khotkeys | Reporter: | Valerio De Angelis <valeriodean> |
Component: | general | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hein, kde, lasse.liehu, mgraesslin, rotter.martinos, valeriodean |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Valerio De Angelis
2014-09-27 08:47:18 UTC
Note: neither with kickoff the shortcuts work. Ressigning to kmenuedit for now, but the real problem has to be somewhere in the global shortcuts system, perhaps khotkeys ... going to read some code. kmenuedit successfully hands the shortcut to khotkeys' kded module, but that's where it disappers. Reassigning to khotkeys ... CC'ing Martin early because I'm now coming across his KGlobalAccel-related porting changes in libkhotkeysprivate. There is some incomplete bits in there, e.g. a connect() to QAction::globalShortcutChanged which doesn't exist, in triggers/shortcut_trigger.cpp. oh I did that, that would have been a stupid mistake. Sorry about that. Could someone please pick it up to fix it? I'll be at a conference starting tomorrow till Saturday and fear that it could fall down the desk with the many things which are on my desk today after a week of vacation ;-) Could [url=https://bugs.kde.org/show_bug.cgi?id=339643]this bug[/url] be related to the same missing code? *** This bug has been marked as a duplicate of bug 337230 *** |