Hi,
At 11:43 AM 5/6/2002 -0500, you wrote:
>>To set a cue point, I need to set the cue points in an external program
>>like Cool Edit first, then re-import the sound file right?
>
>No, you can go into the tempo channel and tell Director to hold on that
>frame until the sound is finished playing or, in the case of QuickTime,
>the 'digital video' in a given channel is finished (Director will treat QT
>audio as digital video).
Under wait for cue point, I changed the cue point from next to end and it
works, the speech file finished playing.
Thank you.
Actually I tried to open the external editor (Cool Edit) from within
Director and the program refused to open with the message not enough
memory or corrupt file. But when I went to start menu to open the program,
there were no problems. I could open it. What happened?
>>>>What is the purpose of using a timer in Director?
>>>
>>>Um, timing things. ;)
>>
>>I gather that you seldom use timers, if at all.
>
>I use them whenever I need to time things. Timers are neither exotic nor
>esoteric. There's no mystery to either their porpose or construction, and
>the reasons for using them are quite straightforward. If you want to time
>things, you use timers.
Sorry, yes I understand it better now.
>>The playhead stops at the next frame. So HALT doesn't affect endSprite.
>
>That's right.
>
>>But I am not sure why- is it because of the loop?
>
>No, it's because when you stop a Director file from playing, whatever
>behaviors might be present on that frame get endSprite messages. If those
>behaviors happen to have endSprite handlers, they execute the code found
>within them.
Am I to understand that endSprite messages will always execute whereas all
other messages will not?
>>The playhead stopped immediately on the next frame and stopped executing
>>the rest of the commands.
>>
>>It is different when compared to 1b above. Is it because the HALT stopped
>>the execution of further commands?
>
>Yes, except for the endSprite call.
But I still do not understand. Why was endSprite executed twice in the
behavior? Isn't endSprite executed once only in a frame span, as
demonstrated earlier?
May I ask you something else? Remember when you were helping me with the
visible and invisible sprites?
The original commands refused to execute. Why was that?
Then you suggested that I place the following commands on the sprite that
I wanted to make visible:
on beginSprite me
sprite(me.spriteNum).visible = FALSE
END beginSprite
on endSprite me
sprite(me.spriteNum).visible = TRUE
END endSprite
Why did you have to do this? I hope that it is not too late to ask you why
but I have been thinking about it. And I still have no answer.
>>>>OnGetPropertyDescriptionList is a system handler. What does this
mean? So there are different types of handlers?
>>>There are indeed. At minimum there are handlers *you* define, such as
the custom ones I made in the volume behavior; and ones that >>>Director is
designed to recognize, such as frame, sprite and mouse events. Of the
latter I believe Macromedia has created several >>>distinctions, but I'm
not sure how well defined those distinctions are.
>>Sorry, but what do you mean by these distinctions are not well defined?
>System handlers versus other types. I'm not sure that the distinctions
are clear.
Sorry, sometimes I do not understand one-line answers. Why do you need to
have the distinctions?
Do not all handlers execute when called?
Thanks for taking the trouble to explain.
Noelle
[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!]
