Xref: utzoo comp.sys.mac:55159 comp.sys.mac.programmer:15208
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!kk
From: kk@mcnc.org (Krzysztof Kozminski)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: There *ARE* uses for forcing the mouse to a location (non-games).
Message-ID: <2294@speedy.mcnc.org>
Date: 8 Jun 90 04:34:41 GMT
References: <2285@speedy.mcnc.org> <17041@phoenix.Princeton.EDU> <2291@speedy.mcnc.org> <1990Jun7.190113.28131@caen.engin.umich.edu>
Reply-To: kk@mcnc.org.UUCP (Krzysztof Kozminski)
Organization: MCNC; RTP, NC
Lines: 48

In article <1990Jun7.190113.28131@caen.engin.umich.edu> billkatt@mondo.engin.umich.edu (billkatt) writes:
>I am using Mac X right now, and it doesn't warp my cursor.  It has a check
>box "Enable Mouse Movement Under Client Control", and I keep it disabled.

Which is EXACTLY what I've been proposing all along.  It was *YOUR*
decision to turn this feature off.  You don't like it - fine, don't use
it, but give the others the same choice that you have exercised  by
disabling this checkbox.  Fair?

>If I want it there I'll put it there.

I couldn't agree more.

>[argument against respositioning the cursor to the next likely check box,
>which was one of my (KK) examples of a possibly useful cursor warp, deleted]

I partially agree - the described method may be confusing indeed.  I
would not write an application that would *force* you to use this
method.  But why do you protest against providing a *CHOICE* for those
who would like to have an option of the interaction I described?  (To
say the truth, these weren't exactly checkboxes, but items functionally
very similar to checkboxes).  BTW, the program that I referred to in my
example is what I think is the singularly most popular schematic
capture package - the exact name of the program withheld to avoid
diverging into an unrelated argument about its popularity - so perhaps
some ideas in its interface are found useful by *some* people.  Now
you're tellng them to go buy an XXX brand workstation, 'cause Mac IIfx
won't be caught dead doing a mouse warp ...

>The mouse pointer belongs to the user.  It should never be moved by the
>program.  If programs start moving it, they user no longer feels they have
>control over what happens.

This happens to be your opinion, shared by many people, but it is not an
universal truth ... please, should I direct followups to talk.religion?

>You should move your windows under the cursor,
>since the windows belong to the program.

Don't you think that many people would be confused if windows started
jumping around?  IMHO, this is way worse than having the pointer do
an occasional warp (but I am not going to protest it as long as I
can disable it on *MY* computer).

KK
-- 
Kris Kozminski   kk@mcnc.org
"The party was a masquerade; the guests were all wearing their faces."