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]
On Jun 26, 2008, at 10:00 AM, Mark Schonewille <[EMAIL PROTECTED]
x-talk.com>
wrote:
Hi Steve,
The cursor changes, but you can't see it. Set the lockCursor to true
or use the command "lock cursor" to keep the new state of the cursor.
Unlock the cursor to see the default cursor(s) again.
--
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 20 jun 2008, at 14:12, stevex64 wrote:
Hi all,
This seems as basic as it can get. I have an image on a
background. On
mouseEnter and mouseLeave it calls a simple handler in the stack
script. The
script uses a switch statement. On mouseEnter I "set cursor to
hand". On
mouseLeave I "set cursor to arrow". I know the script gets executed
because
I put "put" statements in that put unique messages for mouseEnter and
mouseLeave. BUT, the cursor never changes.
Any suggestions?
Thanks!
Steve
_______________________________________________
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
