That (checking all libraries) did the trick. Thanks!
And you were right about why my "clever" little debugging statement didn't work--presumably because the mouseUp handler quit prematurely, although you would think it would not see the RevSpeak command until AFTER it had put the value of whatText into the second field.
Wouldn't it see and execute the put whatText into field "debug" before it even knew there was an unsupported revSpeak out there???
I have SO much to learn! M
On Feb 14, 2004, at 5:30 PM, Dar Scott wrote:
On Saturday, February 14, 2004, at 02:39 PM, Marian Petrides wrote:
In the IDE: the text entered into the first field gets spoken and appears properly in the second field ("debug")
In the standalone: No speech, no text placed into field "debug"
Your example has no 'try' structure. Perhaps your standalone does not have an errorDialog handler. Under those conditions, maybe the error of not finding revSpeak or its not executing completely for some reason, simply causes your mouseUp handler to quit. Under these conditions you might not get any indication of what is happening, except that things stop at a particular point.
Dar Scott
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
