Well I won’t bother trying the press command then
It’s not like I really need it myself.
About the Keeping It Simple principle, yes, that is one of the big strengths of VC.
Personally I think VC/Intag is a must-have for every speech recognition user and definitely the best Dragon add-on out there.
I agree that anyone who doesn’t need custom commands should leave the program as it is, because indeed the featured mouse actions are more than enough for the average user.
At the same time it’s program and folder structure is relatively open for those who want to tweak the program a little. Contrary to Dragon where you can easily screw things up.
About the latter, I think every speech recognition user should have a Partition Image Backup program like True Image (or the built-in image backup from Windows 7/10) in case things go south permanently (for permanently keeping your Dragon activation and Windows activation for instance).
Once both Dragon and VC work properly (and all the rest of your programs) create an image and you’re home free permanently.
"However, when you have just a couple of commands to execute, and in which can be executed almost as quickly as creating a single command"
You have a point there, but when it comes to avoiding voicestrain (which is a real danger) it makes all the difference if you’re uttering these commands all day (less is better). Especially if you cannot use your hands at all and your voice is all that you have left.
"However, one of the most significant caveats is that when you install a new version of VoiceComputer, these commands are not brought over"
Apart from one previous VC version where there was a mistake hiding the intags when an overlay was being called up, I haven’t had any problems with that.
Actually I didn’t use the VC import function for placing my custom XMLs. A while ago I edited displaynumbers, showcustomoverlay and showCustomOverlayactive XML’s (removed/renamed commands I didn’t need and added some new ones, all within the same XML files - didn’t use or create a new one) and stored copies of them on another partition.
Now whenever there is a new version I first configure VC components and commands and backup all original XMLs to a safe place.
After shutting down speech I overwrite the original displaynumbers, showcustomoverlay and showCustomOverlayactive XML’s with my custom onces in both programdata and programfiles 86 folders.
Then I start up VC and everything works great and smooth. Going back to the original files is just as easy. Looks pretty bulletproof, unless of course a new version of VC has a totally different program structure