Hi Peter,
There used to be some problems with cursors, especially in the IDE, in
previous versions. These problems have been solved.
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.
It is also possible to temporarily change the defaultCursor. This
makes locking the cursor unnecessary.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html
for more info.
On 27 jun 2008, at 09:35, Peter Brigham wrote:
I found I was having problems with using the lock cursor technique
in this kind of situation, when the cursor gets locked and doesn't
get unlocked. Once you lock it you have to take on the job of
resetting it for every context, until you unlock it. And then
sometimes for various reasons it stays locked, perhaps because a
rapidly-moving cursor occasionally fails to trigger a mouseLeave
message. I use "set the defaultcursor to hand" then "set the
defaultcursor to empty", which works nicely and lets Rev and/or the
system handle the changes without locking up the cursor.
Peter M. Brigham
[EMAIL PROTECTED]
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
