| Summary: | kconfigupdate script for 4.0.x -> 4.1 for kickoff keyboard shortcut | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | András Manţia <amantia> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | alon.barlev, hendy, usrrgt |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
András Manţia
2008-01-09 18:39:28 UTC
first problem to solve here is: what does "the menu" mean. it's a bit naive to assume kickoff, let alone "that" instance of kickoff. perhaps better is to allow one to define shortcuts per applet and then in the default have a menu entry bound to that. Well yes, in KDE4 you can have multiple menus... But there should be a way to assign shortcuts to Kickoff, Lancelot, traditional menu and the default should be Alt-F1 assigned to Kickoff (as Kickoff is the default menu used in KDE4, right?). I just tried to solve this via khotkeys and a dbus call, but it seems to be not possible, kickoff doesn't have a dbus interface. As an addition: in KDE3, if you add more than one menu to the panel, the first one will be opened with the shortcut. That is a good solution from the user point of view. it's a good solution .. most of the time. and the way to achieve it was a complete hack =) we actually relied on a lot of assumed behaviour (e.g. the "first" menu was also the one that would get created first, etc). i agree it worked pretty damn well, but there were a lot of uncaught corner cases. that said, the kmenu was also *built into* kicker so it was possible to rummaging through all the objects looking for a "k menu". we can do something similar in plasma, but it's even more assumptive to do so. i have some thoughts on how to solve this elegantly, though, and will try and get a patch for it this month. *** Bug 154564 has been marked as a duplicate of this bug. *** Why can't I bind only the Windows key to anything in KDE? Wouldn't it be convinient if the menu could be opened just by pressing that key like in Windows? I realize it would make things "more Windows-ish" etc but the damn key is there. Sitting on my keyboard. Why not utilize it? At the moment you still need another key to be pressed at the same time but that doesn't make a lot of sense. Why not use Alt then. andres: because kde has a policy of not allowing shortcuts consisting only of modifier keys. there's a good reason for it but I'm too tired to explain it properly and this isn't really the place. see also http://docs.kde.org/kde3/en/kdebase/faq/panel.html#id2552742 I miss win-key shortcut for K Menu too. I am a KDE user, but in GNOME is more easy link "win key" to the main menu of GNOME. With 4.1 just around the corner, it's time to close off 4.0 bugs. In the off chance that I'm wrong in believing this to be fixed in 4.1, please reopen. :) And closing... Can you enlighten me how can you access it via shortcut? Which revision is needed? All the necessary parts were put in by Aaron by rev 815055. Just went to confirm to be sure and found that the association is only made when plasma-appletsrc doesn't exist. You should be able to head into System Settings => Keyboard & Mouse => Keyboard Shortcuts => Plasma Workspace => Application Launcher and set up your preferred key combination there. Well, I don't have Application Launcher there to select... And now I have to remove my plasma-appletsrc. Sigh. Will reopen then until at minimum the option is available without removing plasma-appletsrc and preferably the default Alt-F1 set too. Yes, I think it should work with existing configuration, otherwise noone upgrading from KDE 4.0.4 will have the feature. Or a kconfig update script needs to be written. > Or a kconfig update script needs to be written.
this is the only way it's possible.
btw, re-opening bug reports like this is really not great. at the *very* least change the summary so that its apparent what the issue has become. *best* is to open a new bug detailing the new issue, since that way i don't have to wade on through to the bottom of the report to figure out why it's been reopened.
That's arguable and probably a personal preference. :) *** Bug has been marked as fixed ***. This bug isn't fixed! It's well and alive... The "proper" solution is strange: 1. Right click the K Menu / Kickoff, click "Application Launcher Settings" 2. Click "Keyboard Shortcut", assign "Alt+F1", when it says it conflicts with Plasma Workspace Application Launcher, simply click through 3. Click OK and voila! You have your Alt+F1 again And this doesn't make you lose any of your desktop settings. :-) PS. This still happens with KDE 4.2 on PPA repository. (Kubuntu Intrepid 8.10) $ aptitude show kdeplasma-addons Package: kdeplasma-addons State: installed Automatically installed: no Version: 4:4.2.0-0ubuntu1~intrepid1~ppa2 The offending lines (diff format) are here in ".kde/share/config/plasma-appletsrc": [Containments][3][Applets][4][Shortcuts] -global=Alt+F1 +global= See also: https://bugs.launchpad.net/ubuntu/+source/kdeplasma-addons/+bug/271622 |