Copyright 2002-2015 Rick Mohr
 

Writing Vocola commands is straightforward with a little practice. This page summarizes some potential problems, and how to solve them.

My command doesn't work

You've written a Vocola command but nothing happens when you speak the command. Here are some possible causes:

  1. You didn't save the .vcl file.
  2. Your command had a syntax error.
  3. You're speaking the command in a different context than you defined it for.
  4. You changed an include file (.vch) and didn't run the Vocola translator by saying "Load All Voice Commands".
  5. Your command is in a filename which contains a character other than a digit, letter, or underscore before the @ or extension (.vcl); older versions of NatLink (before May 2007) are known to have a bug which causes them to ignore such files. Either switch to a later version of NatLink or use a different file name -- this may require renaming the executable if the offending character occurs in its name.
  6. NatLink didn't load the translated Python file.
  7. Your command uses a non-written out number (e.g., "3" rather than "three").

My command doesn't work right

Your command gets executed, but doesn't work correctly. Here are some possible causes:
  1. Another command is being executed instead.
  2. You need to use quotation marks in your Vocola command. Quotation mark delimiters are usually optional in Vocola, but are required in some cases:
  3. You need to use SendSystemKeys or SendInput to get Windows or some applications to see some keystrokes. For example, the Window key shortcuts require this. Thus, to pull up an explorer window, you can use SendSystemKeys({win+e}). Note that SendSystemKeys is substantially slower than Dragon's normal method of sending keystrokes so should be used only when needed.