From kde-core-devel Mon Jul 22 15:59:08 2002 From: "Aaron J. Seigo" Date: Mon, 22 Jul 2002 15:59:08 +0000 To: kde-core-devel Subject: Re: [PATCH]: menu button in window deco X-MARC-Message: https://marc.info/?l=kde-core-devel&m=102735361401170 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 21 July 2002 09:00, Thomas Zander wrote: > > this is a good question. it's an obvous usability abomination. > > Why do you think that? for all the reasons i stated in my original email. > Its a feature, just like double clicking a word > selects that word, and triple clicking selects line. Its not invasive for > users that don't use it and quite usable for people that do. It is > annoying some times that you hit the triple click while you only wanted the > double click. single/double/triple select are not: a) destructive tasks b) overloaded on a single GUI item c) break style guidelines. d) hidden behind the guise of something not related to selection your example is not like the double click close at all. > Misfeature or not, the people that do rely on that behavior will not like > it at all if you remove it. Its quite easy to gain a bad name in the UI > department, and rather hard to get rid of it. In this case it really is the > safest path to follow the former leaders. (i.e. ALL of them :) right. a sanely working menu button that follows KDE's style guides (e.g. click on it again and the menu disappears) would be far too confusing! thousands of double clicking closers the world over would stop dead in their tracks wondering just to do next. ;-) > Is there any problem with it staying? Do you get bug reports that people > lost work because of this? Is the bug really this behavior, or did an > application forget to ask to saved unsaved work? not all windows have the concept of "unsaved work". i discovered this behaviour by having my IRC session closed on me (bye-bye history, hello reloging in!). konqueror, kdict, kmail and a host of other apps that are used as viewers rather than editors will just close silently. while you don't lose "work" you do lose time and there is a real level of agravation if closing the window isn't what you wanted. as for bug reports, i've received at least one from one of the people who rely on me here for tech support. i had no idea what he was talking about at the time ("i clicked on the title bar a couple of times by accident and the window just dissapeared!") but now i do =) he's an ex-windows user, but not a power user. the double click thing is probalby as foreign to him as it is to me, despite him being an ex-windowser .. > > ok. if decided, i'll remove it everywhere. > > I think you read CTs email the way you wanted to, since I do believe he > only pointed out the problems with the removal of this feature. So > concluding that the feature should be removed seems a bit hasty :) no, i said "if decided" not "since it is decided" .. meaning that *if* it were decided that this is a good thing, that i would follow his suggestion to make everything follow the same method. btw, BII doesn't have the double-click close in CVS, so if we want consistency and stick with double-click close that ought to be fixed as well... pretty simple to do ... > Please don't remove the feature, it only makes it harder for recovering > Windows users :) fine. consider the topic dead. two people voiced their opinion aginst it (and one in private, to make three), nobody for it (well, save me obviously ;) ... game, set, match. next! - -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 "Everything should be made as simple as possible, but not simpler" - Albert Einstein -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9PCvN1rcusafx20MRAhcaAJ9GyY8hI7BbMdyXq7AEzLafzCG/VwCgqOqJ j6KUKS0xNcvSCCj/znzMyKM= =bZs/ -----END PGP SIGNATURE-----