https://bugs.kde.org/show_bug.cgi?id=194438--- Comment #3 from Thomas Lübking <thomas luebking web de> 2009-06-06 22:05:34 ---
windows has no menu button, but just a window icon - kwin provides a menu
button that - in many cases - actually paints the icon as well and is by this
used to play the window icon role as well.
applying this to a window icon is unfortunately neither w/o problems.
1. right clicking the entire deco currently shows the menu, left clicking it
enters moving and double clicking does configurable stuff (maximizing, shading,
...stuff) and different from windows the titlebar layout isn't fixed (i.e.
assume title and icon centered (e.g. check the keramik deco)
so the icon could easily be dbl.clicked by accident
2. many decos would have to replace the menu button or live with the fact of a
minimum 2 button requirement to access the menu (and where apple just dropped
out - in a way - touchscreens drop in...)
just for curiosity: what's the point about having an item on the titlebar that
1. behaves different from all others (double instead of single click)
2. this way triggers an inreversible action (closing)
3. (in case of icon and many decos) does not indicate it's active state on
hovering (and in relation to e.g. taskbars will easily be taken as simple
indicator)
4. is redundant to a dedicated item that explicitly indicates the resulting
action?
hint: "windows does it" does not count ;-P
--
Configure bugmail:
https://bugs.kde.org/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are watching all bug changes.
