At 23:03 +0800 04/29/2002, noelle cheng wrote:
>But may I know that if the introduction of the movie was something
>like a presentation, i.e. it runs from the score with no lingo ,
>how do I make the movie pause at certain frames, say frame 30, 50
>and 90? I can't use the pause command. I use the property pendTicks
>as below?
That would be one way to do it, sure -- you'd then be able to have
the playback hold on a given frame for a few seconds.
>Why did my playhead stop at frame 140 and refuse to move?
That's not an answerable question. You're encountering difficulties
that could be due to a fairly wide range of things, and unfortunately
notes sent to a list really are not sufficient to debug the issue.
>However, I note that for the script in frame 139 below, the script
>window shows global. I tried to change it to 'exit frame' but this
>refused to work. However, in the PI the cast member was behavior.
>Which is correct?
What script window shows 'global'? What do you mean 'refused to
work'? Part of the reason it's difficult to offer useful answers is
that it's not always clear what the questions are, and in what
context the script and code you're describing is being used.
If possible please try to use terms such as Cast and Score when you
are referring to Director's control interface; describing what you
are doing in the Cast or Score is vital to expressing the context in
which these events occur. Things aren't just done somewhere in
Director; they are done in specific parts of the program, using
specific tools in specific fashions.
As an example, you need to be able to know what the three script
types are, how to recognize them, and which type is to be used in
given circumstances. (How? Practice, working from scratch on your own
files and your own code, getting familiar with Director and its
interface and its tools.) You also need to be able to recognize when
a behavior has been properly attached to a sprite, and whether you
are in fact using a behavior as opposed to a movie (or Cast member)
script.
Without this understanding it will be very hard to offer meaningful
suggestions, because it will not be clear to you what is meant by a
given suggestion, and it will be difficult for you to express how and
where things are breaking down. You'll end up trying lots of
different things in lots of different ways, nothing will work or
(worse) things will work intermittently, and you'll be relegated to
frustrated thrashing.
This is not your fault; in an attempt to become easy to use computers
have also tried to become modeless (edit mode versus read mode, for
instance, is a thing of the past with text editors and word
processors). This is fine if one is not doing anything particularly
complicated, but with Director one certainly is, and its non-modality
makes it very easy, until you are familiar and comfortable with the
user interface, to become confused regarding whether a given
operation affects the Cast, the Score, the Stage, or some combination
of these; and whether you're entering a movie script, parent script,
Cast member script or behavior.
>3. Could be due to a loop on frame 140 - a 'go the frame script'
>
>No, and none of the sprites on frame 140 had that line either.
Is 140 the last frame in the Score window? Director will get to the
end of that and simply stop operating unless there's some kind of
code there to keep it going. Your program might have fallen off the
edge of the world, as it were.
>But I have a sound file which contains some speech at frame 143.
>That's why I inserted Irv's script at frame 140.
Do you have a go the frame script in frame 143?
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://www.osborne.com/indexes/beginners_guides.shtml
[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!]
