As was mentioned, look for a halt command.
Another simple answer is, if you normally have the movie loop around, and you accidentally turned off the "loop" button on the control panel, then it will go once through the frames with sprites (unless you have a go to the frame command to force a loop) and when it runs out of sprite frames, it will call stopMovie.
It's a little hard to say without seeing the movie and/or knowing how it's structured.
- Tab
At 08:52 PM 12/22/03, Bruce Mitchener wrote:
Tab Julius wrote:Does it die with a crash, or just stop responding?
For most of today and last night, Director was just fine afterwards. It responded okay, nothing crashed.
The problem is that Director acts like I (or someone) hit the "stop" button and stopped the movie while it was playing. It is running, it gets through a couple of iterations of that frame and then it just stops.
If it dies, you can narrow it down by bracketing it until you find the place that is causing its death.
If it just stops responding, my guess is that you might have an infinite loop, which would be hard to further diagnose without the movie itself.
As above, it is just stopping. A trace shows something that is like this in terms of things happening:
* exitFrame on sprite X runs. * exitFrame on sprite X + 1 runs. * exitFrame on sprite X + 5 runs. * stopMovie runs.
After some other bug fixes and attempts to fix things, during the whole stopMovie process, it is closing down the 3D sprite, destroying lots of stuff, and in *that* process, I crash Director. But I often crash Director while closing down a 3D sprite in development, so that's nothing atypical/unusual, and it wasn't crashing for last night or the vast majority of today.
- Bruce
[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!]
