SayWhatPro Command Help (V2.1)

File menu Edit menu View menu Dvcfile Program Scope Group Pro Help menu

File

Open: This command will allow you to open a macro command file (.dat) other than the current user's mycmds.dat. It is very handy for looking at the contents of Exported .dat files (or files you are about to Import).

Print COMMAND list: This command will print a report that is basically a listing of COMMANDS (and/or LISTS) with MENU and STATE headings.You always wanted a way to get a list of COMMANDS didn't you?

Export to dvc: This command will create a syntactically correct Dragon .dvc file. Handy for sharing or moving macros.

Export to pseudo dvc: This command will create a file in the legacy dvc format, but will also contain the new version 6 style commands (Advanced Scripting, etc.) as well. This is especially handy for studying groups of the new style commands. Of course, do not try to import this file.

Export to spreadsheet: This command will create a comma delimited file (.csv) capable of being imported into a spreadsheet.; The 3 previous commands all allow their output to contain one of the following:

Everything--All user and Dragon-supplied macros
Just this app--Only the commands in the current application
Just this STATE--Only the commands in the current STATE
Pick and Choose--You can select any or all of the commands in the current STATE

Also, any output can be sent to the printer, to a file which can be user specified, or to the Windows Clipboard.; In addition, the scope of the print/export will conform to the current View (below).

Refresh after Dragon Browser update: Use this if you leave SayWhatProPro open while making a change (or addition) with the NatSpeak Wizards (or directly editing .dvc files) that you want to see reflected in SayWhatPro. Unnecessary if SayWhatPro is closed during Wizard (or user) updates since SayWhatPro will automatically detect any changes when firing up again. Also use this to go back to your main production mycmds.dat file after doing a File, Open.

Re-Specify DNS path: Use this if you have multiple installations of NatSpeak and SayWhatPro uses the wrong one (rare).


Restore mycmds.dat (previously called Rollback): Available for Registered users only. The first time each day that you use SayWhatPro to make a modification to the current users mycmds.dat file, SayWhatPro makes a backup copy of your mycmds.dat file in a subdirectory with the name of your user in the SayWhatPro installation directory. If for some reason, you need to rollback your mycmds.dat file to an earlier version, this is the command for you. I have never seen SayWhatPro damage my mycmds.dat file (even in my rawest debugging stage). However, the mycmds.dat file for people who would likely use this program is the result of many (sometimes hundreds) of hours of labor. It is simply too valuable to take chances with. Even if you are not a registered user, I urge you to back up this file.

Backup dvc file: Registered users only. This command forces SayWhatPro to make a backup of the current dvc file immediately. It will overwrite if a copy has already been made according to the description in the previous paragraph. Use this command when you want to do something (Ex. Importing an unfamiliar or large command file) that you may want to be able to essentially undo by using the Restore command above.

Restore dvc file: Available for Registered users only. The first time each day that you use SayWhatPro to make a modification to the current dvc file, SayWhatPro makes a backup copy of your that dvc file in a subdirectory with the name of your user in the SayWhatPro installation directory. If for some reason, you need to rollback this dvc file to an earlier version, this is the command for you.

Edit

Find: Search through all .dvcs for strings contained in:

COMMAND or LIST names
body of COMMANDS or LISTS
specific STATE names

Match case--you may select to search for an exact case match.
: You may search repeatedly forward and backward with "Find Again" (or F11 key) and "Find Previous" (or F12 key).

Options: Change SayWhatPro options

Browser to use for updating. dmcbrowser no longer works for the NaturallySpeaking update 6.1. Command Browser may be used with both versions although I have encountered a bug in the 6.0 Command Browser for some Deletes.. Because of its slow loading time, Command Browser should be left open (but not minimized) between updates. Minimal command delay for dmcbrowser is 200 milliseconds (.2 seconds), for Command Browser it is 500 milliseconds (.5 sec.)
Browser Command delay. This is the amount of time for each step of an update process to pause so that the user may see what is actually happening indicate Dragon Browser. The initial amount of time is 2000 milliseconds (2 seconds). Once the user gets comfortable with the process, this amount may be reduced for minimal delay.
Wizard Command delay. This is the amount of time for each step of a mapped dvc file update using the Wizard. The initial amount of time is 1000 milliseconds (1 second). Once the user gets comfortable with the process, this amount may be reduced for minimal delay.

View

By Application (the default--formerly Appmode): Display all commands relating to a particular application. The File: text box will display the actual filename where the command comes from.

By dvc file (formerly Dvcmode): Use this mode to display only commands from 1 .dvc file. For some (most) applications, this will not be any different than By Application. This mode is much less useful in version 6 than it was in version 5 but has been retained for those occasions when still necessary.

KEYs: Toggle on/off to show/not show KEYS type COMMANDs

SCRIPTs: Toggle on/off to show/not show SCRIPT type COMMANDs

LISTs: Toggle on/off to show/not show LISTs

Text and Graphics: Toggle on/off to show/not show Text and Graphic Commands

Macro Recorder: Toggle on/off to show/not show Macro Recorder Commands

Step-by-step: Toggle on/off to show/not show Step-by-step Commands

Advanced Scripting: Toggle on/off to show/not show Advanced Scripting Commands

All of the above: Turns on all KEYS, SCRIPTS, Text and Graphics, Macro recorder, Step-by-step, Advanced Scripting and LISTs

Only 1 of the above: Drops down a list to pick only 1 of the above. This makes it very easy to turn off all of the above except for one type.

Legacy DVC File(s): Toggle on/off to show/not show macros in actual DVC files that are mapped thru the system wide dvcmap.ini file. By default, there is only 1 file--system.dvc.

MyCmds.dat: Toggle on/off to show/not show macros contained in mycmds.dat (the main production macro file for this user).


1 COMMAND with its LISTs: This is handy for easily viewing only 1 COMMAND and its referenced LISTs. Example: if the cursor were highlighting the following command:; <SelectOrDelete> <NextOrPrevious> <2To20> Words; When this command is selected, only 4 entries will be shown in the list:

<SelectOrDelete> <NextOrPrevious> <2To20> Words
SelectOrDelete
NextOrPrevious
2To20

This makes it much easier to study individual components of a particular command. When this mode is active, Exporting can also only apply to this View if desired. This is especially handy for sending 1 command and all it's LISTs to another person or to be included in an e-mail message.

1 LIST with calling COMMANDS: This is sort of the corollary of the above. When this View mode is invoked with a LIST highlighted, it will then show all COMMANDS that reference that LIST.

Description: Now you can choose whether or not to view a commands Description on the SayWhatPro screen.

Dvcfile

This command is not available unless "View by dvc file" is activated. When activated, this menu contains a list of all the individual defined .dvc files both user and Dragon supplied. Choosing one will make the displayed list of macros contain only macros from the chosen .dvc file.

Program

This command allows you to choose which application (MENU) to display macros for. Everyone has a Global Commands application.

Scope

This command allows you to choose the Scope to display from the current application. I have defined an application-specific STATE for newly created application-specific macros.

Group

This command allows you to choose which Group to display. Everyone has at least 2 groups (Dragon and User-defined) and more if you have defined them. Think of this menu item as being similar to the View menu.

Pro

This command allows access to the various registered functions.

Edit: If this command type is editable by SayWhatPro, the cursor will move to the macro body box for editing. At the current time, KEYS, SCRIPT, LISTs, and Advanced Scripting commands can be edited directly in SayWhatPro. You can now edit Application-specific legacy commands.

Clone: Often times when I want to write a new macro, I will realize that I have an already existing macro that would only take a small amount of modification to achieve some new result. This command allows you to clone (make a copy of) an original command with a new name. Then you can edit this new cloned command, saving perhaps many steps of a creation process. Macro Recorder commands are unable to be edited even by the Dragon built-in process. Another possible use for this command is when you want to have another command phrase to perform the identical action as another command phrase. All commands are always cloned to the mycmds.dat file, even if the original command is in a mapped dvc file.

New Legacy KEYS: Easily create old-style KEYS commands in the current Application and STATE. With the registered version's supplied importable macros, it is easy to dictate key sequences of the following type: {Ctrl+f} "control key plus foxtrot" and {Alt+d} "Alt key plus delta"

New Legacy SCRIPT: Easily create old-style SCRIPT commands in the current Application and STATE. Registered version SayWhatPro supplied macros make it easy to dictate all of the built-in Scripting commands (SendKeys, AppBringup, etc). A full DVC SCRIPT syntax check is made before allowing you to commit the macro. Newly created legacy dvc commands are available for execution immediately.

New Advanced Scripting: This command actually immediately brings up the MyCommands Editor. Create the name of your macro and be sure to specify Scope if not Global. If you need to specify an object to work on, do it at this time, otherwise leave the body of the macro as is, Click/Say Save, and return to SayWhatPro for dictating the actual body of the macro. The registered version macros can be used here also. At this time, no syntax checking can be done by SayWhatPro. However, it causes no harm to save a syntactically incorrect macro. It will of course, give you an error when you invoke your macro.

New LIST: This command prompts you for a new LIST name and immediately you can enter the LIST values in the normal SayWhatPro editable textbox (and then say "Save Changes").

Delete: This command will find the current command with the specified browser and bring up the Delete dialogue. It will pause for an extra 5 seconds for you to confirm that the correct command has been found. If for some reason it is not the right command, choose the default "No" during that 5 seconds. (This has not happened to me at all, but I have set it up this way to be extra safe). Even command names with uppercase letters in them can be found by SayWhatPro with dmcbrowser. If this command is in a mapped dvc file, SayWhatPro will bring up the Edit Command Wizard, and delete it essentially as above.

Edit with Dragon: This command will find the current command with the specified browser and bring up the MyCommands Editor. Even command names with uppercase letters in them can be found by SayWhatPro with dmcbrowser.

Train: This command will find the current command with the specified browser and bring up the Dragon Train dialog.

Help

About: Information about SayWhatPro.

Command Help: This document.

License: The fun part.