Script cast member not found

Question

Can anyone tell me why the %^$& I get a "script cast
member not found"
error?
I've been working in Director for 17 years and I get this
from time to time.
I generally just copy the code from the behavior, paste it
into a new
behavior, name the new one the same as the old on, then copy
the new cast
member over the old one and it solves it. But it happened
rarely enough
that I didn't bother questioning why. I know it's not a
syntax error
because the code runs fine after the above process. But it
does only
happens when I've made a change to the code in that behavior.
Now I'm working with a simple movie with one parent script
and a
prepareMovie handler that instantiates one child object and
I'm getting this
darn error all the time. My above solution isn't working
anymore. The
error points to the first line of a particular handler. That
first line was
a comment. So I got rid of the comment and the new first line
of the
handler is code and the error points to it. If you see where
I'm headding,
no matter how many lines of "errored" code I get rid of the
error alert will
always point to the first line of that handler.
I'm sure many have seen this because it's happened in almost
every version
of Director I've owned. And by the way, I'm in MX on a PC.
Craig Wollman
Lingo Specialist
Word of Mouth Productions
212-928-9581
www.wordofmouthpros.com

Answer 1

Dean, I might do that. No, this has been going on long enough
that I sure
it's not any definable user error.
But, I did, after all of these years, discover something last
night. In one
case, I did get a legitimate script error that I fixed. When
I ran the
project again, I received the same script error, even though
it was a simple
fix and I was sure I corrected it. I recompiled several times
and ran it
again and received the error again. Then it dawned on me that
since parent
scripts remain in memory until disposed of, Director must
have been, for
some reason, referring to the old parent script. I had
already set the
object's global variable to 0 in my stopMovie handler and
even though that
handler might not always run when errors occur, I ran it from
the message
window to insure that the object's global was 0. But that
still didn't
solve the problem. Then I used clearGlobals in the message
window and
voila, the issue went away. Dare I say that this is a
shortcoming of
Lingo's design to allow variables to persist/linger after an
error?
But what still baffles me is that most of the time when I get
that
particular error,, even though I seemed to have found a
workaround, it is
not an actual issue with any code.
When it happens again, I'll send you the code. Obviously, if
I'm correct
about the scripts lingering in memory, then you won't receive
the error when
you run the movie.
I just find it interesting that there haven't been a bunch of
"Yeah, I get
that darn thing too" here.
Craig
Craig Wollman
Lingo Specialist
Word of Mouth Productions
212-928-9581
www.wordofmouthpros.com
"Dean Utian" <[email protected]> wrote in message
news:[email protected]...
> Hi Craig,
>
> Could it be a simple mistake of the script type not
being properly defined
> (movie/parent/behavior)?
>
> If you have a very baic movie where this error occurs
repeatedly, you
> could
> email me ([email protected]) and I'll take a fresh
perspective look at
> it.
>
> regards
> Dean
>
> Director Lecturer / Consultant
>
http://www.fbe.unsw.edu.au/learning/director
>
http://www.multimediacreative.com.au
>
>
>
>