On Fri, 29 Mar 2002, Tab Julius wrote: > I have a number of scenarios where a window tells the stage to do something > which turns around and tells the window to do something, etc. In theory > this should all work as it's all nested, etc. However, in projectors (on > Windows only - not on Mac), what I'm finding is that every once in a while, > a message gets delivered to the wrong window.
I've given off on telling stages and windows unless I'm sending to objects. Here's the way I do things now. 1. Sprite on the stage has a behavior that instantiates a MIAW. 2. That MIAW loads with all its command code as behaviors, either in channel 0 (framescript) or one or more sprite channels. 3. When I want to communicate with the MIAW, the sprite behavior that owns it gets a message. That behavior then sends a message to the acceptor behavior in tnhe MIAW. 4. The MIAW, when it is answering, sends its response to the owning behavior on the Stage (or whatever instantiated it). 5. When the sprite ends it tells the mIAW to go to a close frame (which has no sprites on it, but simply a 'go the frame' handler), after which it does a close and forget. I've got some pretty dang involved MIAW files going now with a joyous lack of crashage, freezage and general Director-flavored befuddlement. Perhaps this approach would be more effective for you, if you haven't done it already? Gots ter love dem dere OOP. :) -- WthmO [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!]
