[Bug 154485] do not zoom out maintenance buttons

[Sebastian Sauer]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=154485         




------- Additional Comments From mail dipe org  2008-02-26 15:58 -------
> why, exactly? (other than "everything should be configurable")

Something goes wrong if things start to popup/fade in/blink/trade your soul with a donut/etc just cause you moved your mouse. Just moving the mouse should never lead to actions without an option to turn that behavior off.

Also why should somebody lose a corner that could be else used to e.g. activate a kwin-effect, to turn on the screensaver, to switch (in future) between plasma views, etc.

> in xinerama set ups you lose the fitts law nature of the corners, but i don't see a real issue here. 

Cause someone needs to be able to define at which output-medium the toolbox got displayed since they probably don't wanna have it e.g. at tv-out, at a monitor-station, small devices, presentation mode aka presenter view, not at montor #1 but at monitor #2, etc.

Guess one of the problems is, that there is just no information around what this thing is for and a "you will see" is hard to take cause "we already see" and what is visible so far did already lead to massive feedback and it's needed to deal with that feedback somehow and may it only to collect the points. To just say "nada, nada, I'll not listen and do what I like to do" misses the "it's all about the users" as well as the "be free" points. Hell, even Microsoft does listen (if you have enough money or are able to put pressure on them). What is done out of it, is written down on another piece of paper (and in the case of MS the result mostly sucks even more, heh).

>> for the kiosk-mode 
> this would be instrumenting the zoom buttons, then, not the toolbox. 

and a toolbox without any buttons/functionality makes no sense. Sometimes it's wanted to provide just _no_ functionality except starting and closing some programs.

> there is not enough information on the table to make this decision at this point. 

yeah, cause it's work on progress, as sayed on bug #154535 already, and there still stays a lot of time to s/WTF\?/WOW!/gi;

Well, it's not about decisions anyway. It's all about not wasting more time with this and to provide a way users can offer feedback somehow and somewhere as well as to let them know, that work is done there and the current state is only a temp one.