I am running the latest version of VoiceComputer. I have had no trouble using in tags on an open menu. Now, using every command, it no longer works. Hopefully, I can attach the open menu.
I think that you need to use “Configure VoiceComputer” to import your previous Overlay commands, etc.
Thank you for getting back to me, Ron,
Your previous Overlay commands are in the CustomOverlays.xml file located in the
Thanks for getting back to me, Ron,
First, provided that you have copied the right file, you still have to "restart speech" in order to have it take effect. Just copying the file and expecting VoiceComputer to launch it is insufficient. Because of the way that these commands work, when you make a change and try to continue working in VoiceComputer, it's not loaded.
Second, provided that you copied to correct file from the correct backup, check it. I found on occasion, when I import my VoiceComputer configuration files, I have selected the wrong backup file. The bottom line is always compare the file that you are copying to the file that is in your "VoiceComputer" folder. Sometimes it's easy to make a mistake. Always check the date and size of both files.Chucker2016-09-01 08:44:53
Browse to C:ProgramDataVoiceTeach and you’ll see the VoiceComputer.bkx directories
Why does not it show up in my documents when I attempt to import commands?Because it’s under C:ProgramDataVoiceTeach.(The next release will point to this directory instead of displaying My Documents.)>By the way, this is not a custom command. It was just simply having the menu open and> saying show intags and up they popped.It’s a set of custom overlays (My Tags).
Let’s try to have Chuck give you a tech support call tomorrow.
For everyone's edification, the problem that Jim was having had to do with display settings in Windows 7, along with making configuration changes in VoiceComputer.
Everyone should be careful to note that there are some display resolution conditions under which InTags will not display correctly. This has to do with Windows, not VoiceComputer.
At any rate, problem resolved.
Thanks for the assistance, Chucker.