Version: (using KDE 4.0.82) plasmoid should follow the settings for window behaviour for example: auto-raise -- I set it off for purpose, yet, plasmoid violates this settings and behaves exactly opposite.
What do you mean?
Now I am puzzled how to explain this :-) auto-raise off -> windows are _not_ auto-raised auto-raise off -> plasmoids _are_ auto-raised I simply wish for consistency.
hum.... plasmoids are not windows! =)
> plasmoid should follow the settings for window behaviour Since when stuff that is clearly not a window should behave like it is? Plasmoids are not windows, they not even have any relation with them. And, they even have a quite different look than windows. You wish for "consistency"? You have it, non-windows don't behave like windows, simple and easy.
Of course they are not windows, but: a) current behaviour is hard-coded b) there is no configuration for widgets c) why user sets for example "auto-raise" off? because it is harder for him/her to work with auto-rise on I could rephrase the wish like this: please provide configurable widget behaviour
it's an object model on a canvas, not a windowing system. going that route is a sure pathway to madness for the codebase and interaction.
Aaron, but you realize that you force of UI mode _you_ like to all the KDE users. If auto-raise is the only true way it should be dropped from SS for windows -- after all it is superior to raise-on-demand. Not irony, but simple consequence. Either user is in control, or KDE is. I don't see any benefit for user if he/she has to struggle in two modes at the same time (and one of the modes is she/he dislikes). Auto-raise also causes common problems when managing widgets. And one more thing -- for code (internally) there could be plasmoids, windows. For user there are just objects. > madness for the codebase and interaction. One consistent mode is madness? I see madness right now, because object on my desktop behave in two different ways.