Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!vsi1!apple!lsr
From: lsr@Apple.com (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: moving mouse pointer under program control
Message-ID: <630@internal.Apple.COM>
Date: 10 Feb 89 01:28:04 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 29
References:<17871@gatech.edu> <6443@hoptoad.uucp> <1858@helios.ee.lbl.gov> <6476@hoptoad.uucp>

TIm is exactly right when he points out the compatibility dangers of 
moving the mouse under program control.  If you are doing this for a 
personal program, then go ahead and blast away at low memory.  Just don't 
complain to us if it breaks in a future system.  

If you are doing this in a program that you distribute widely, then think 
twice.  At least, mention this "feature" or provide a way to turn it off.  

I personally would hesitate to use a program that moves the mouse 
programmatically.  For one thing, I hate when a program "takes control" of 
the cursor.  (The old FEdit did this when it hid the cursor while starting 
up.)  

Also, I wouldn't be able to trust a program that moved the mouse 
programatically.  (What other evil things might it do?)  I have come to 
realize that when choosing software, it is best to consider the quality of 
the program and/or the reputation of the programmer(s), even over the feature lists.

The only quibbles I have with Tim's message are (1) I don't think you 
could implement a mouse replacement soley by patching traps (GetMouse, 
Button, et al); you would need to replace the cursor handling code as 
well, and (2) I think GetMouse, Button, et al are more likely to be "come 
from" patched that he says.


Larry Rosenstein, Apple Computer, Inc.

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1