property spriteNum
on beginSprite me sprite(spriteNum).cursor = 280 --anything else you want to do here end
on endSprite me sprite(spriteNum).cursor = 0 -- -1 sometimes screws things up later -- anything else you want to do here end
This way, there is no need to set and reset in every mouseEnter and mouseLeave.
Irv
At 9:58 AM -0500 12/21/04, Slava Paperno wrote:
At 01:55 PM 12/21/04 +0000, Chirs wrote:What kind of sprites are these? Flash? QT? Bitmaps? Just trying to rule out DTS effects...
How about using "sprite(n).cursor = x" instead? As far as I recall, this is the preferred syntax, and "cursor x" can cause problems when called more than a certain number of times.
Thanks, Chris--they're 32-bit bitmaps imported as png's, with transparency. The syntaxt change doesn't help, and I've pretty much ruled out everything else, including all exitFrame loops.... Still struggling. I think the fact that this is happening on G4s and not G5s may have to do with processor speed...
S.On Monday, December 20, 2004, at 08:51 PM, Slava Paperno wrote:
I'm seeing weird mouse pointer/cursor behavior that I can't shake. On a G4 and Powerbook running 10.3.x and 10.2.x, in Shockwave (IE 5.2 and Safari 1.2.x) when the mouse pointer enters a sprite with a mouseEnter handler that changes the cursor shape to "cursor 280", the cursor keeps alternating between the default arrow and the 280 (pointing finger).
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
--
Multimedia Wrangler. [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
