On Mon, 03 Nov 1997 19:21:21 -0500 (EST), you wrote:
> Now for the discussion part.... The original Usenet poster stated
>the principle thus:
>
>> "Under no circumstances whatsoever should a windowing system allow
>> the keyboard focus to move other than as the result of explict user
>> action."
>
> While this sounds nice in principle - and I often have similar
>feelings when confronted by the excesses of the in-your-face,
>spoiled-child school of application programming - it's not so good in
>actual practice. (I think the term "explicit user action" may be
>open to a bit of fuzzy interpretation here.)
>
> I played around with the "ReallyStrictClickToFocus" idea on my
>test system over the weekend, and the results were generally unsatisfying.
>For keyboard oriented apps like editors and word processors, you usually
>*do* want them to receive focus when they pop up a new window. With my
>"ReallyStrict" version, I still found myself typing into the wrong
>windows - just different wrong windows under different circumstances.
>Likewise, most of the time when you take an explicit action - like clicking
>on "Find" in Netscape - that causes a transient to pop up, you tend to
>expect it to get focus without having to tell it so by clicking on it. I
>don't think anyone would be terribly happy if the "ReallyStrict" focus
>policy were forced on all applications.
Could clicking "find" in netscrape be considered an "explicit user action"?
Dale
--
Dale P. Smith
dale.smith_at_bellhow.com
Cleveland Linux Users Group: http://cleveland.lug.net/
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Nov 04 1997 - 07:18:49 GMT