Registering and logging in removes this ad.
Registering and logging in removes this ad.
vocola with DNS 10
Submitted by dkehler on Wed, 08/20/2008 - 19:53.
I was wondering if anybody had an idea how to get working with DNS 10?
CLI and Python
Submitted by gilbertpremo on Thu, 08/21/2008 - 23:52.
1. What brings up the CLI in this case? Is it, in fact, a DOS window?
2. I don't know why Python would come up during macro editing, it doesn't usually, but the buzof.exe program
from Basta Computing, http://www.basta.com
can automatically close any annoying and unwanted window.
In this case, the CLI was
Submitted by dkehler on Fri, 08/22/2008 - 00:27.
In this case, the CLI was initiated by myself as part of the configuration of natlink/vocola as part of Quintijn's install package.
The messages from Python window comes up whenever there is an error message or some such, like a syntax error in a vocola macro, for example. However, the way Quintijn has it set up (at least as far as I can tell), it wants to use simpscrp as default for entering new vocola macros but apparently, it fails sometimes and the backup default is notepad, but in doing so, it generates a message window telling me that it is using Notepad. It's not a huge deal, but it would be nice not to have to close that window every time I want to edit a macro. However, I don't want to ALWAYS automatically close it in case an important message shows up.
Hello all, I'm sorry to note
Submitted by Quintijn on Fri, 08/22/2008 - 09:42.
Hello all,
I'm sorry to note there are a few stupid remarks on this thread. Please study the installation and configuration pages.
1. The window "Messages from Python Macros" should always appear when natlink starts. Regardless whether unimacro and/or vocola are activated. This window should remain on. If you close it, it will reappear whenever some macro action, either from vocola or from unimacro writes something to it. Note vocola cannot work without natlink/natpython.
2. I updated the page which the instructions for the command line interface (CLI). The letters you use can also be obtained by the command letter "u", but I provide them here for convenience.
3. So, with the "S" command you turn off simpscrp. With the "w" command you can specify a path for your vocola commands editor. Do not forget to use double quotes if the path to your editor contains spaces.
4. Simpscrp was not my invention, but is a heritage from the vocola developers. I didn't write vocola, but provided unimacro, the installer, and a lot of improvements for a smoother interaction between vocola and natlink.
That is why details on installation and configuration are now found on the unimacro website.
5. I am sorry the configuration GUI does not work on some installations. The GUI makes configuration a lot easier, the CLI is only meant as a way to do things if the GUI fails.
If somebody can trace the spot where it goes wrong I can possibly provide a solution. Known is, you best take python 2.3.5, see the installation instructions.
Quintijn
Quote: I actually went
Submitted by MarkUK on Wed, 08/27/2008 - 16:17.
I actually went through the process of replacing notepad.exe with the notepad 2 executable, which involves "fooling" windows into allowing the change because Windows treats Notepad as a critical system file and immediately restores it if you tried to replace it with something else. There are a few step by step guides on how to get around this if you do a search.
There was a much simpler way to do this with 2.6, Tools|Folder options|File Types, find .vcl and change the "Opens with" to Notepad2, browsing for the executable.
MarkUK wrote: Quote: I
Submitted by dkehler on Wed, 08/27/2008 - 17:18.
I actually went through the process of replacing notepad.exe with the notepad 2 executable, which involves "fooling" windows into allowing the change because Windows treats Notepad as a critical system file and immediately restores it if you tried to replace it with something else. There are a few step by step guides on how to get around this if you do a search.
There was a much simpler way to do this with 2.6, Tools|Folder options|File Types, find .vcl and change the "Opens with" to Notepad2, browsing for the executable.
Actually, that was the first thing I tried and it didn't work. But then again, I didn't know how to disable simpscrp at that time.
Well, for solving all these
Submitted by Quintijn on Wed, 08/27/2008 - 18:01.
Well, for solving all these sort of troubles, _vocola_main is designed to open the command files in a suitable editor, which can be chosen by the natlink/vocola/unimacro configure program.
So what is the problem?
Quintijn
Quintijn wrote: Well, for
Submitted by dkehler on Wed, 08/27/2008 - 18:07.
Well, for solving all these sort of troubles, _vocola_main is designed to open the command files in a suitable editor, which can be chosen by the natlink/vocola/unimacro configure program.
So what is the problem?
Quintijn
The problem was I didn't know how to do that. Never had to do it before.
if you use multiple words with dgnwords
Submitted by reckoner on Wed, 09/24/2008 - 13:12.
Note that you also have to change the dgndictation references and VocolaUtils.py and in the vcl2py.pl perl script. In particular, in the vcl2py.pl script, you'll need to make the change to get
} elsif ($term->{TYPE} eq "dictation") {emit(0, "+ ")}
note the "+" sign in . You will need that if you want commands like
do <_anything> = type $1;
to work like
"do one two three"
and then emit "one two three" instead of just "one".
Do you have version 10 of
Do you have version 10 of DNS?
Yes, got it today.
Yes, got it today.
I'm not sure that anyone on
I'm not sure that anyone on here that's using Vocola has DNS 10 yet...
Guess we'll find out together!
beta release natlink 3.3
Although I do not have NatSpeak 10 yet, I tried to make a release with NatSpeak 10 defined in the natlinkstatus.py module.
You can try this one, please report if you succeed or have install problems.
See:
http://qh.antenna.nl/unimacro/installation/install...
Quintijn
Okay, here's what I did. I
Okay, here's what I did.
I uninstalled natlink/vocola.
I installed the beta release natlink 3.3
I ran the configuration CLI and assigned the vocola directory
I registered the natlink DLL and got a success message
I restarted NaturallySpeaking but that didn't work so I rebooted my computer and still vocola does not respond.
The CLI information screen appears to show everything correctly (i.e. the NaturallySpeaking install directory etc.)
What am I missing?
First thing is: is the
First thing is: is the Messages for Python Macros window coming up?
Second thing: can you copy the contents of the log window of the configure GUI or the output of the CLI?
Quintijn
I don't know what the
I don't know what the messages for Python macros window is.
The configure GUI doesn't appear to work. All I get is a window that briefly appears and disappears.
I'm not sure how to copy the contents of the output of the CLI, but I notice that it says that natlink is disabled.
What should I do next?
And by the way, thank you for trying to help.
Success! I enabled natlink
Success!
I enabled natlink with the "e" command in the CLI window, restarted NaturallySpeaking and now vocola works!
Okay, one more thing: How do
Okay, one more thing:
How do I disable simscrp so that I can use Notepad2? I have installed notepad2 and associated VCL files with its executable but if I say "edit global commands," it still opens up with the regular Notepad.
Happy to hear it works.
Happy to hear it works. Answer your question tomorrow,
Quintijn
Thank you for your help!
Thank you for your help! With respect to the Notepad issue, what I ended up doing is replacing Notepad.exe with the Notepad2.exe (which isn't as easy as it sounds) but I have it working now.
Is there a way to suppress the message in the "messages from python macros" window (I know what you meant now) whenever I'm simply trying to edit vocola commands?
Update
Vocola commands that capture dictation with the <_anything> parameter don't appear to be working. The following error message is generated.
Traceback (most recent call last):
File "C:\natlink\natlink\macrosystem\core\natlinkutils.py", line 492, in resultsCallback
fullResults.append( ( x[0], self.ruleMap[x[1]] ) )
KeyError: 1000000
Graphic configuration and <_anything> do not work
My experience was very similar to yours.
I installed setup-natlink-3.3.beta.exe
The graphic interface configuration did not work. It just flashes a small (DOS?) window, which disappears and does nothing. The CLI did not work either.
The file "C:\natlink\natlink\confignatlinkvocolaunimacro\natlinkconfigfunctions.py" had to be opened in Phytonwin.
Don't known too much about Phythonwin, but the interactive window reported that Phyton was looking for Natlink in C:\natlink\natlink\macrosystem\core, and the Registry had Natlink in another place.
I did not uninstall the earlier Natlink before installing 3.3, so this was probably the problem, even though I did reboot after installation.
I edited the Registry per the error message and per the text in the top of the .py file which says the DNS [sic] Install Directory can be set in HKEY_CURRENT_USER\Software\NatLink. I set:
HKEY_CURRENT_USER\Software\NatLink\UserDirectory to point to: c:\natlink\natlink\macrosystem\core
and entered "e" in the {F5} window in Phythonwin, and Natlink/Vocola then worked.
After the Registry hacks, the GUI still did not work, but the CLI worked.
"Edit Voice Commands" does bring up Notepad instead of Notepad2. How did you replace Notepad.exe with vcledit.exe?
Bppt into DOS? Notepad.exe does not seem willing to die.
The Vocola <_anything> command no longer works in DNS 10. The following error message appears:
Traceback (most recent call last):
File "c:\natlink\natlink\macrosystem\core\natlinkutils.py", line 492, in resultsCallback
fullResults.append( ( x[0], self.ruleMap[x[1]] ) )
KeyError: 1000000
I actually went through the
I actually went through the process of replacing notepad.exe with the notepad 2 executable, which involves "fooling" windows into allowing the change because Windows treats Notepad as a critical system file and immediately restores it if you tried to replace it with something else. There are a few step by step guides on how to get around this if you do a search.
I hope that someone who knows what they are doing is able to get the <_anything> parameter working at some point because it is a very useful feature, but for now, I am just glad that vocola plays nice with DNS 10 for the most part. Although at this point, you need to be sufficiently motivated to get it to work.
Replace of Notepad
OK,Thanks. Replaced it.
gilbertpremo wrote: Don't
Don't known too much about Phythonwin, but the interactive window reported that Phyton was looking for Natlink in C:\natlink\natlink\macrosystem\core, and the Registry had Natlink in another place.
You probably installed natlink3.3 in another directory. In that case you should accept the new location and proceed.
I did not uninstall the earlier Natlink before installing 3.3, so this was probably the problem, even though I did reboot after installation.
No, you could have installed in the same directory as before.
I edited the Registry per the error message and per the text in the top of the .py file which says the DNS [sic] Install Directory can be set in HKEY_CURRENT_USER\Software\NatLink. I set:
HKEY_CURRENT_USER\Software\NatLink\UserDirectory to point to: c:\natlink\natlink\macrosystem\core
You are messing up things this way
"Edit Voice Commands" does bring up Notepad instead of Notepad2. How did you replace Notepad.exe with vcledit.exe?
Bppt into DOS? Notepad.exe does not seem willing to die.
See my other message, but when you mess up the settings, things could become unpredictable.
The Vocola <_anything> command no longer works in DNS 10. The following error message appears:
That is a serious error.
Quintijn
"No, you could have
"No, you could have installed in the same directory as before."
The instructions for 3.3 said to install in C:\Natlink, so I did.
That was not the same directory as I had it in before.
Then you should follow the
Then you should follow the instructions the config GUI of CLI gives!
Quintijn
This error will require more
The Vocola <_anything> command no longer works in DNS 10. The following error message appears:
Traceback (most recent call last):
File "c:\natlink\natlink\macrosystem\core\natlinkutils.py", line 492, in resultsCallback
fullResults.append( ( x[0], self.ruleMap[x[1]] ) )
KeyError: 1000000
This error will require more effort. Also for the vocola developers probably, which I am not.
I can not look at it yet, as I have not yet NatSpeak 10.
Quintijn
A little more information
I am seeing the same error with the following configuration:
DNS 10
NatLink enabled (the newest version)
Vocola disabled
Unimacro disabled
It occurs when I attempt to use the Hungarian command in the _ProgrammingNotation.py NatLink file. My suspicion is that the error is being caused by the grammar that is used by that file.
I don't know this, but it would not surprise me if the grammar is what underlies the <_anything> command in Vocola.
This is a bit unusual
This is a bit unusual configuration. But if in you grammar
<dgndictation> imported;
is present, you are correct. That is the same rule as the <_anything> command in vocola.
Quintijn
<_anything> works now!
Vocola commands that capture dictation with the <_anything> parameter don't appear to be working. The following error message is generated.
Traceback (most recent call last):
File "C:\natlink\natlink\macrosystem\core\natlinkutils.py", line 492, in resultsCallback
fullResults.append( ( x[0], self.ruleMap[x[1]] ) )
KeyError: 1000000
Note that I'm referring to DNS 10 Pro. I got the same error reported above, but when I went through the generated vocola files and changed dgndictation to dgnwords, everything works great!
I hope somebody can verify this. There needs to be a change in the perl vcl2py.pl script to make this change automatically generated.
good news! Otherwise, DNS10 is not so great. Just a little zippier with better HTML/browser navigation.
reckoner wrote: dkehler
Vocola commands that capture dictation with the <_anything> parameter don't appear to be working. The following error message is generated.
Traceback (most recent call last):
File "C:\natlink\natlink\macrosystem\core\natlinkutils.py", line 492, in resultsCallback
fullResults.append( ( x[0], self.ruleMap[x[1]] ) )
KeyError: 1000000
Note that I'm referring to DNS 10 Pro. I got the same error reported above, but when I went through the generated vocola files and changed dgndictation to dgnwords, everything works great!
I hope somebody can verify this. There needs to be a change in the perl vcl2py.pl script to make this change automatically generated.
good news! Otherwise, DNS10 is not so great. Just a little zippier with better HTML/browser navigation.
That is great news. I too, hope someone else will verify this. I now have to re-think my upgrade plans.
Good work,
-Coop
Can you specifically tell me
Can you specifically tell me exactly what I need to do/change to try this out?
Edit: Nevermind, I figured it out. And yes, it does work!
if you use multiple words with dgnwords
Note that you also have to change the dgndictation references and VocolaUtils.py and in the vcl2py.pl perl script. In particular, in the vcl2py.pl script, you'll need to make the change to get
} elsif ($term->{TYPE} eq "dictation") {emit(0, "<dgnwords>+ ")}note the "+" sign in
<dgnwords>. You will need that if you want commands likedo <_anything> = type $1;to work like
"do one two three"
and then emit "one two three" instead of just "one".
Good work reckoner,
Good work reckoner, thanks.
Another question: Will the old installer work with DNS 10 with the edits you have outlined? I just find it easier to use (and understand).
TIA,
-Coop
Coop wrote: Good work
Good work reckoner, thanks.
Another question: Will the old installer work with DNS 10 with the edits you have outlined? I just find it easier to use (and understand).
TIA,
-Coop
if you are talking about the configureNatlink installer from Scott, then it should work. That's the one I'm using.
reckoner wrote: if you are
if you are talking about the configureNatlink installer from Scott, then it should work. That's the one I'm using.
Yes, that's the one I mean.
Thanks,
-Coop
How about dgnletters?
Thanks for this tip. The only thing I would add is that I needed to recompile the vcl2py.pl script into a new vcl2py.exe and overwrite the existing one. To do this I had to find Cava Packager (http://www.cava.co.uk/) and download Perl (http://www.activestate.com/Products/activeperl/ind...) and use Cava Packager to create the new exe. Maybe I'm missing some major aspect of how vcl2py.pl works, but this is what I did to eventually get things working.
Now I'm experiencing similar problems with my Python macros that make use of <dgnletters>. I'm actually receiving the same above error message. Does anyone have any idea how to get this to work with DNS 10? Thanks.
Can you specifically tell us?
For those of us who haven't figured it out, can you please
specifically tell us exactly what we need to do/change to try this out?
Thank uys.
What's a CLI?
What's a CLI?
Commandline interface. Like
Commandline interface. Like a DOS window.