>The puppetTempo is set after any go command and used in a movie script?
You can use puppetTempo any time. You can use it in a frame script, for
example, to temporarily slow down or speed up the frame rate. You could
even use it in a behavior on a sprite.
>Why is it unnecessary to turn off the puppet tempo condition to make
>subsequent tempo changes in the Score take effect?
PuppetTempo only temporarily overrides the script tempo. When the tempo is
set in the tempo channel, that has the effect of overriding the last
puppetTempo.
>>if gPausing = TRUE then go the frame
>
>
>-- end if should be added here
Good catch--NOT! You only need the end if when the "if" and actions are on
separate lines. Two ways of doing the same thing:
if gPausing = TRUE then
go the frame
end if
if gPausing = TRUE then go the frame --all on one line
I usually use the first format because it makes the code easier to read.
>This script only works if there is a button on screen to click e.g. a skip
>introduction button. So , it is not quite useful when there are no bitmaps etc.
As it's written, yes. But use your imagination. You could put up a little
bit of text that says "Click anywhere to continue" with this frame script
on exitFrame
go the frame
end
on mouseUp
go the frame + 1
end
>Why do you specify that sprite 0 is a sprite channel?
Did I say sprite channel? I meant script channel. A frame script can be
addressed as sprite 0.
>>- stretch out the sprite spans
>
>3. Won't it make the score longer? Also, in doing this, the tempo is
>still not fixed and the movie would still have different speeds when
>played on different machines.
Yes, it will make the score longer. I virtually never use it, but that's my
style.
I think of Director users as basically two types--programmers and
designers. A designer has better things to do with his/her time than a
bunch of complicated programming stuff that stifles the right brain, so
they're more likely to do score-based stuff. Both styles are equally valid.
It's like the old saying--there are three types of people: those who can
count, and those who can't.
>4. May I not not use timeOut as an event Handler specifing timeout Length
>as a property?
Sorry, you lost me there.
>New Timeout = timeout("myTimeout")
>In this case, how is the object used?
You have to specify a period, in milliseconds. I like dot syntax, so I
would do something like this
timeOut("bideAWee").new(5000, #goNext)
on goNext
go to "nextPage"
end
This tells Director to wait 5 seconds (5000 milliseconds), then execute the
handler "goNext." Note that this is a pretty simple example. If you don't
tell Director to stop the timeOut object, it will keep calling the goNext
handler every 5 seconds. You use "forget" to stop the timer. I think I gave
an example earlier in this thread.
Anyway, I have managed to find out that startTimer can be used. Of course,
the script is not as elegant as yours, however.
>on exitFrame me
> if the timer<60*5 then
> go to the frame
> end if
>
>end
Yes, that will do it. TimeOut objects are actually easier to use, though,
once you get the hang of them, and a lot more reliable.
I'm going to be off-list tomorrow--we're celebrating our 26th anniversary.
I'll be back on line on Wednesday or Thursday, though.
Cordially,
Kerry Thompson
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]
