This issue has come up again. Would someone from the UI team please read this user’s comments and tell them whether they’ve made a case for double-clicking the menu button to close a window, and why or why not? Also, can people from anywhere downstream confirm there that downstream patch inclusion is not necessarily caused by upstream patch inclusion? (I know that sounds obvious, but I’m from upstream so it’s less believable if I say it.)
In other news, Launchpad bug 160311 might have persuaded me to make window borders resizable for accessibility separately from the theme. Any accessibility experts who’d like to weigh in on this one are welcome.
This is turning into the Metacity Journal, isn’t it? Sorry.
A: Let’s introduce stupid feature F copied from Microsoft into GNOME!
B: Uh, I don’t know, it’s kinda lame…
A: But, but… If we don’t then newcomers from Microsoft will feel ALIENATED and go back to Microsoft!
B: Ah, OK then…
I don’t think I like the logic of this discussion. This time it’s closing by clicking the top-left corner, next time it will be something even more ridiculous. What ever happened to aiming for quality instead of user-quantity? If devs really want to replicate every quirk of Windows then they should go write ReactOS.
I’m not on the UI team, but please _don’t_ copy the feature from Windows. The cost a user pays when they accidentally close a window far outweighs the advantages. Not many Windows users I know are even aware that the feature is there.
@Natan: I’m interested to know which applications these are which allow data loss by accidental closing of a window (without a dialogue to ask whether the action was deliberate).
The ‘copied from MS’ argument is just plain wrong. Double-click to close was in OS/2 Presentation Manager,in CDE, in God knows how many other graphical environments.