use-revolution digest, Vol 1 #1558 - 17 msgs

Jim Hurley jhurley at infostations.com
Wed Jul 2 05:53:01 EDT 2003


>
>Message: 11
>Date: Wed, 02 Jul 2003 00:25:24 -0400
>Subject: Re: Speaking of voices
>From: Ken Norris <pixelbird at interisland.net>
>To: <use-revolution at lists.runrev.com>
>Reply-To: use-revolution at lists.runrev.com
>
>Hi Jim,
>
>Well, if I'm right, the explanation might be a little hard to follow, so
>hang in there.
>
>According to the docs, the line in question (RevSetSpeechVoice "Bruce")
>cannot change voices while speech is already happening in a given session,
>i.e., if you _were_ changing voices, which it must account for even if you
>don't.
>
>Therefore, "revSetSpeechVoice" behaves like the beginning of a sequence at
>every encounter in the current session, meaning it's going to shut off any
>running speech when it sets the voice. This is "normal" in this case.
>
>Thus, setting the voice _first_ causes the current speech to stop in
>preparation for the next revSpeak command. After the line executes, there is
>no more speech, i.e., revIsSpeaking() is FALSE. You can check this in the
>message box.
>
>Your handler:
>
>on mouseUP
>   revsetspeechVoice "Bruce"
>        ## Kills the speech
>
>     if revIsSpeaking() then
>       revstopSpeech
>           ## revIsSpeaking is now FALSE because the first line
>           ## already killed speech.
>
>     else revspeak me
>        ## Will always start speaking at the beginning.
>
>end mouseUP

Ken,

Makes eminent good sense! Thank you. I had misunderstood your 
original message to say that revsetspeechvoice somehow affected the 
usual logic of the if...then...else control.




More information about the use-livecode mailing list