At 11:28 +1300 03/15/2002, Sean Wilson wrote:
>Would anyone else care to confirm that opening a MIAW from the stage's
>prepareMovie handler causes the MIAW's prepareMovie handler to fail?
>And when run as a projector, the openWindow, prepareMovie and beginSprite
>(for a sprite in frame 1) events display a different order from the
>authoring environment?
>
>A workaround is obvious - open it from startMovie. I didn't expect this and
>hadn't read about it elsewhere.
Actually a better workaround is to not use movie scripts at all and
instantiate your MIAWs from sprite behaviors or in the script
channel. You cna put a beginSprite event into the framescript, for
instance, thus:
PROPERTY pwMyWindow
on beginSprite me
pwMyWindow = window "Sean"
pwMyWindow.filename = whatever
pwMyWindow.type = whatever
open pwMyWindow
END beginSprite
on exitFrame me
go the frame
END exitFrame
on endSprite me
pwMyWindow.close()
pwMyWindow.forget()
END endSprite
You can do similar things in the framescript for your window file.
This allows you to get out of prepareMovie, startMovie, stopMovie and
so on, and allows you further to treat your windows as OOP objects.
Stability issues become minimal when you do that.
The one caveat is that you can have only one behavior in the
framescript channel. The behavior can be referenced by doing
sendSprite to sprite 0, which is pretty convenient.
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://www.osborne.com/indexes/beginners_guides.shtml
[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!]
