Version: (using KDE KDE 3.97.0) Installed from: SuSE RPMs Classic KMenu: it is not that I am used to it, it is simply this Novell discovery is less productive. Two simple cases: * you know in advance where the item is -- Novell KMenu is cooler and takes less space on the screen * you don't know in advance where are you going -- Novell Kmenu forces users to click much more and to move mouse much more (think: handicapped people) Switch: in opensuse (KDE3) it is enough to RMB on the KMenu icon and choose the mode. Note: I am not saying classic KMenu is good, productive, etc. It is not productive. But Novell Kmenu is even less productive.
Just add an "Application Launcher Menu" applet to have a kde3-like menu.
The panel gets broken if you do that ( but this is an different bug ) Anyway I think he meant ' Add the an *option* to switch the menus' eg; klick on that and you switch from kickoff to classic one. Right now kickoff is hardcoded in the panel and if you remove it you have edit the plasma configs 'manually' and *pray* it does work when you add other widgets / plasmoind, So I really wonder how you can say that works ?
> The panel gets broken if you do that ( but this is an different bug ) > Right now kickoff is hardcoded in the panel and if you remove it you have > edit the plasma configs 'manually' and *pray* it does work when you add > other widgets / plasmoind, So I really wonder how you can say that works ? Both are not related to the problem. > Anyway I think he meant ' Add the an *option* to switch the menus' > eg; klick on that and you switch from kickoff to classic one. Do we really need that? Do you switch menu type so often, that you need a visible option?
(Accidentally reopened, re-closing.)
Pino is right, there is a way to do the switch (and you don't do the switches too often). Indeed, opensuse is easier here, but how much gain is that in two years you do 2 clicks instead of one. Another story is malfunctioning switch -- but this not not about this report. Worksforme, I would say (ah, you were faster).
yes, such a mode change would be a violation of a plasma principle (objects should not have global mode switches but exist as separate objects). c.f. the clocks for another example of this principle in action.
4.0 is now out, and you could have -labeled- the classic menu better. I didn't even realize it -was- what 'the classic menu' everyone talks about elsewhere is until you stated it here. Even looking at it, it's still missing several things I want, but I guess from what I've read you'd consider those generic plasma improvements. It Really could use autohide and I'd like that for all my other widgets too (at least as an option I could set a global default for, and alter on a case by case basis).
Switching back and forth between the "Kickoff" menu style and the "Classic" menu style (indeed, as discussed elsewhere, better names could be found. May I suggest "Tab" and "Tree" menu styles...), there is a bug to report: The application launcher settings are forgotten or reset to default values in both cases. As a concrete example, I am very annoyed by the "switch tabs on hover" option, that I must therefore systematically re-deactivate after switching menu styles.
Alan, true, but do not hijack reports -- please open another one about the issue you mentioned, thank you.