My colleague's Mac is TRWTF
-
What can DIAF is focus-follows-pointer + window-to-front-when-focus.
Focus-follows-mouse when it requires you to point directly into the entry field is the worst of the worst. You won't find apps that work that way these days precisely because it sucks so much. (Knock the mouse slightly? That keyboard input is going to somewhere else! Gaaah! )
-
This. Keyboard input focus should only change from an intentional action like hitting a keyboard shortcut or clicking the mouse. Not from a possibly-unintentional slight mouse movement, and certainly never without user action at all like from a new application starting up ( )
-
I do however like scrollwheel follows pointer.
I find it somewhat annoying that it only works sometimes under Windows.
-
and certainly never without user action at all like from a new application starting up ( )
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
That's an instant way to make me kill your application with prejudice.
-
Unfortunately, it's the norm on windows.
-
Yes, yes it is...
-
Keyboard input focus should only change from an intentional action (…) and certainly never without user action at all like from a new application starting up
Are you saying you expect a newly-started application to not come to the front, and for one of its windows to not become the active one after it finishes starting?
-
yes
-
If I start an application, then continue to work in a different (already open) window, then the new application should not come to the front.
The application should only gain focus if I did not perform any actions (relevant to focus) after starting it.
-
the traditional desktop metaphor.
Nobody likes it.
Apple have finally gone full retard with OS names.
I thought that happened back when they named their OS after this guy:
-
Agreed — but your original statement made it seem like you expect a new application always start behind whichever ones you were using before, which had me wondering.
-
-
Also, "Windows maximizes everything" is a strawman, no one does that.
True, but Windows 8 maximises more things than it damn well should.
Other than this, it's managed to not upset me a great deal.
-
You would have liked the Xerox PARC. Overlapping windows is something they added to the PARC ideas, the PARC didn't have 'em.
??? – Overlapping documents (windows) was the central idea of Kay's desktop metaphor.
[Edit] Interestingly, this was apparently present in the developing LISA-OS even before the famous PARC visit.
(Compare the copy text by Andy Hertzfeld to a set of LISA development screenshots:
"...into a mouse/windows based user interface. This is obviously the biggest single jump in the entire set of photographs, and the place where I most wish that Bill [Atkinson ] had dated them. It's tempting to say that the change was caused by the famous Xerox PARC visit, which took place in mid-December 1979, but Bill thinks that the windows predated that, although he can't say for sure." – http://www.folklore.org/StoryView.py?story=Busy_Being_Born.txt)
-
Kind of, but it didn't redraw background applications, it left them blank.
-
Which might have been due to the limitations of the hardware. Going to keeping non-foreground contents visible is a trivial extension of the metaphor, since that's what happens with stacks of physical paper on a desk.
-
This is, where "regions" came in. – Obviously this didn't matter much to the visual behavior, since Apple folks were under the impression that PARC had solved the problem.
As for Xerox, impressive and important work was actually done at SDD (Systems Development Department, El Segundo) when defining the Star's interface. This one came with tiling windows by default but could be switched to overlapping windows by a user setting.
BTW: We're generally forgetting about Bell Labs and Blit in this context (which was apparently suffering from the same problem of redrawing partially revealed regions).