Hi Mauricio,
Thanks for that info. I never do put any sprites in frame 1 but have been burned by not remembering the event order during inter-movie navigation and I think that's what I ulitmately wanted to point out that it is not just a frame 1 issue but a _first_ frame issue and event order planning is important to sort that out.
I most definitely never have any xtra sprites sitting in frame 1 so I've never thought about the problem from the xtra point of view. Even with internavigation movies I don't think I ever navigate directly to a frame holding an xtra sprite, I assume that would cause the same kind of grief and an invisible frame 1 would not fix the issue in that case either.
-Rob
On Thu, 19 May 2005 14:17:30 -0300, Mauricio Piacentini <[EMAIL PROTECTED]> wrote:
You might be right if you consider only Lingo, but some of these subtle issues affect C++ code inside Xtras (3rd party or from Macromedia.) The internal MOA interface does not have a prepareMovie, the MOA sprite/asset events are the same since Director 5. Xtra sprites are initialized in paused state when on frame 1, among other differences. I understand that a fix would potentially break existing content as well, so...
I don't think there is an easy way out for this issue, or MM would certainly have implemented it so far (having an invisible frame 1 on the score was a suggestion at some point in the past, but it could break stuff like score recording IIRC.) I remember discussing frame 1 issues with engineers since D5, and they are still around today. Nowadays I just assume everyone is aware of problems with content in frame 1 and start placing scripts and Xtra sprites on frame 2...
[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!]
