setting pointer location

Bill Vlahos bvlahos at
Sat Dec 28 15:24:03 EST 2002

I don't know if this is a good idea or not but it might be worth 

Instead of relocating the mouse, simply hide it until it is moved. That 
way the user doesn't really seem to start from the same location even 
though they actually are. Each question would present the user with no 
predetermined location for the mouse as the first time they see it it 
would be moving.

I'm not really thrilled with either this or the idea of relocating the 
mouse which I've seen in some of Microsoft's dialogs (which drive me 
nuts). However, in your situation something like this may make sense.

Bill Vlahos

On Saturday, December 28, 2002, at 11:30  AM, DVGlasgow at wrote:

> I know moving the pointer is generally a no no, and I thought twice 
> before
> doing it.  However, I accurately time the latency of assessees rating 
> an
> image.  If they move the pointer between images being displayed, the 
> time
> taken to return the pointer to the scale would add an abitrary  amount 
> to the
> latency.  So, the procedure is.
> Countdown  target appears (like in old movies)
> image appears at target location
> cursor appears at scale midpoint
> rating made (and latency calculated)
> 'next image' button appears
> 'next image'  button hit
> image and 'next image' button disappear
> Countdown target....
> etc. etc.
> Any suggestions for alternative approaches that are  less naughty 
> welcome.

More information about the Use-livecode mailing list