(Well, a lot of the Flash in Director is weird...can't issue a go to frame X command from a flash callback, have to set a 1ms timeout object to do it, etc. But right now I'm talking about a weird cursor issue.)
Flash is sending a message to the Director Behavior attached to the sprite. It sends messages such as "CursorOn" and "CursorOff". I'm setting the cursor 'cursor 280' and 'cursor -1' when I receive these.
That works great. (Which is sort of weird behavior.)
But, If you click on another window in Authoring, or another program in projector, the cursor no longer responds to the FLASH-originated calls, though it still receives the messages, goes beep if I have the code go 'beep' after the cursor line, etc. And the Director-originated cursor controls still work fine.
Is this another issue with Flash-originated events?
What's the deal with Flash-originated events not being able to do everything?
roymeo
----------- Roy Crisman Macromedia Director Programmer, Lingo Guru, Multimedia Producer Greater Rochester Macromedia User Group (GRMMUG.org) Coordinator 277 N. Goodman St. Rochester, NY 14607-1162 (585)473-3492 home roymeo(AT)brokenoffcarantenna.com
[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!]
