"aplWin" wrote in message news:112b5553-2d90-4165-89f5-3d81833ad25b@googlegroups.com...
Why are you using a 'Form'?
I had thought of testing the response handler by outputting the recogonised text to the Form.
>Instead of
>'fm.wordsRule' Œwi 'xInitialState.AddWordTransition' '' 'one'
>try
>'fm.wordsRule' Œwi 'xInitialState.AddWordTransition' ('#' Œwi 'empty') 'one'
Since my last post I managed to get the function to run all the way through to hearing the spoken text without APL throwing an error by replacing '' by 0 (zero) in the problem line. The returns from running the function were:
fm
fm.speaker
fm.listener
fm.context
fm.grammar
fm.wordsRule
0 ¯2147352572
0 ¯2147352572
0 ¯2147352572
1
The three 0 ¯2147352572 returns look like error codes from the problem lines but so far I have not found a translation for them. As I have not gone through the speech recognition process set up yet on this machine I am hoping that might be the cause as I keep getting prompts to do so.
Trying your suggestion results in exactly the same output.
>Also refer to
>https://support.microsoft.com/en-us/help/12427/windows-speech-recognition->commands
>Would work with Windows 7
OK will do. Thanks for your patience and help with this problem. I would like to see the original problem through to a final solution as it is proving to be a valuable learning excercise.
Graham.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
|