Rev Built-in cursors IDs

Eric Chatonet eric.chatonet at
Fri Oct 21 12:48:57 EDT 2005

Hi Lynch,

Would you mean:
put the ID of image "magnifier win.gif" of card "card id 1002" of  
stack "revCustomCursors" into tID :-)
A bit long for my brains...
And if, in a further version, Runrev changed the name of this stack  
too? ;-)
I prefer import the image by myself...
Just me and the engine!

Best Regards from Paris,

Eric Chatonet.

Le 21 oct. 05 à 18:11, Lynch, Jonathan a écrit :

> You can do this:
> Put the ID of image "whatever cursor" of card "myCard" of stack
> "myStack" into tID
> Set the cursor to tID
> This way, it figures out the right ID number whenever it switches
> cursors - thus avoiding a problem if the ID has changed.
> -----Original Message-----
> From: use-revolution-bounces at
> [mailto:use-revolution-bounces at] On Behalf Of Eric
> Chatonet
> Sent: Friday, October 21, 2005 11:52 AM
> To: How to use Revolution
> Cc: Runtime Revolution Support
> Subject: Rev Built-in cursors IDs
> Hi all,
> All built-in cursors IDs have been changed between Rev 2.6 and 2.6.1.
> For instance ID 202619 has been changed for 76 and there is no
> numeric relation between the old and the new ones.
> This is not important for standalones but is really annoying for
> stacks, utilities, plugins, etc.
> I know that ID 1 to 100 are theoretically reserved for built-in  
> cursors.
> This feature was not respected: Now it is and you have to revise all
> your stuff  :-(
> The lesson seems to be: don't trust the image library provided by
> RunRev and import by yourself all needed images into a stack if you
> don't plan to make a standalone ;-)
> Best Regards from Paris,
> Eric Chatonet.

So Smart Software

For institutions, companies and associations
Built-to-order applications: management, multimedia, internet, etc.
Windows, Mac OS and Linux... With the French touch

Free plugins and tutorials on my website
Web site
Email        eric.chatonet at
Phone        33 (0)1 43 31 77 62
Mobile        33 (0)6 20 74 50 86

More information about the Use-livecode mailing list