This content has been marked as final. Show 2 replies
In your startMovie handler, put this:
That way, once the projector starts, you will have a message window. It
is not a full debugger, but it certainly helps. Remember to set it back
to 0 when you do your final build of course!
> In your startMovie handler, put this:
> the debugPlaybackEnabled=1
> That way, once the projector starts, you will have a message window. It
> is not a full debugger, but it certainly helps. Remember to set it back
> to 0 when you do your final build of course!
I tried that. Doesn't work. I can't type in the Message Window because
there's an error message that displays every frame, and it's modal, and
won't let you type anywhere. As soon as you make the error message go away,
a new one crops up, so you never get a chance to actually USE the Message
Window for anything.
For the record, I did solve the problem in this case by sheer luck - I
happened to notice that the FileIO Xtra was suddenly not included in the
Projector, so it wasn't loading any of the data it needed, thus leaving
several key property lists empty, hence "Object expected" and "Index out of
range". This is pretty weird as the Xtra WAS included before, and I haven't
changed anything in the included Xtras list in weeks, and I've created and
tested dozens of projectors since then without a problem, so I don't get why
this is suddenly cropping up NOW. Anybody ever heard of any case where a
Director project suddenly forgets which Xtras it's supposed to have loaded?
(And yes, I'm fully aware that I should probably remove all Xtras from the
list and store copies of them in an Xtras folder with the movie - I may just
do that to prevent this particular bug from occuring again.)