Very simple cursor problem

[Peter Brigham]

On Jun 27, 2008, at 10:00 AM, Mark Schonewille <m.schonewille at economy- 
x-talk.com> wrote:

> There used to be some problems with cursors, especially in the IDE, in
> previous versions. These problems have been solved.

Not completely. I have run into occasions when the cursor remains  
"stuck" despite my never having locked it, both in the IDE and in  
standalones -- it seems to occur sometimes when changing substacks or  
resuming Rev or the app. OSX 10.4.1, Studio 2.9 build 610. I still  
haven't gotten to the bottom of this. It's possible that I have a  
lock cursor command left in some script in the hierarchy. But there  
have been a couple of times when even sending "unlock cursor" from  
the message box doesn't change the cursor back to default mode.

> I never use mouseLeave and mouseEnter messages to set the cursor,
> because these are unreliable. If I do rely on the mouseEnter message
> (e.g. to show a pop-up window), I use the send (in time) command to
> hide the window. You could do the same with cursors.

Interesting. How exactly do you change cursors, eg, for rollover  
effects, if not by mouseenter/mouseleave? Do you use mousemove? And  
what difference would the "send in time" command make?

> It is also possible to temporarily change the defaultCursor. This
> makes locking the cursor unnecessary.

That's the point of my previous message. These days I try never to  
lock the cursor, I set the defaultcursor instead.

Peter M. Brigham
pmbrig at gmail.com