SayWhatPro FAQ

Q. Where is the macro description field displayed?

A. Beginning in version 2.1, now that the complete form is resizable, viewing of the macro Description field is enabled by default. You can turn it on and off, through the View Menu.

Q. Why did you use such an ugly font to display the macro body?

A. That ugly font is the fixed space Courier New. "Fixed space" is the keyword here. You will never make another mistake about whether/how many spaces something has in it. Have you ever had trouble figuring out consecutive intermingled single and double quote marks? Never again.

Q. Why is there no Rename function in the Pro menu? I'd like to rename a command from SayWhatPro.

A. I could have enabled that function in SayWhatPro, but it is just as easy for anyone to do Pro, Edit with Dragon. This will bring up the Dragon MyCommands Editor for the current command, and you are automatically positioned on the commandname, where it is easy to modify the name. For commands that have LIST names in them, say/click "Name Editor"

Q. At the end of a "Save Changes" cycle, I get a message that SayWhatPro is already running, but I just enter and go on.

A. This is caused by an interaction with the way that you start up SayWhatPro, and the AppSwapWith command that SayWhatPro uses to return control to itself after controlling Command Browser. It only happens when you say "Start say what pro". Even this method will not have this problem if you create a SayWhatPro shortcut on the desktop. The recommended way to start SayWhatPro is by using the commands "global say what pro" or "local say what pro" that are documented on the installation page (and which were originally legacy AppBringUp commands, but which are now Advanced Scripting Shell commands). You may download these two commands here.

Q. SayWhatPro brings up Command Browser, and positions the mouse pointer, but it misses Import (or something else), and then hangs. It was previously working correctly.

A. There are 2 possible causes for this problem. Make sure that your Command Browser window is large enough to display Import on the right, and Next on the bottom. Actually, on the bottom, below Next, make the window tall enough so that the vertical scroll bar on the right hand side of the window becomes greyed out. Otherwise, you can inadvertently scroll in the Command Browser window, causing SayWhatPro to miss its mark. The other thing that can cause problems (believe it or not!) is Internet Explorer(IE). You may have heard the term HTML-based in relation to Command Browser. In IE, if you change the setting under View, Text size, it will also change the size of the text in the Command Browser window. Settings of Largest and Larger caused problems with SayWhatPro before version 2.21. Starting with this version, any and all settings of Text size are handled properly. I have found that it is possible to accidentally change this setting with inadvertent mouse movements in IE. SayWhatPro will account for this setting, although if a change is toward the Larger sizes, it is possible that your window size for Command Browser will no longer show everything, or activate the vertical scroll bar, introducing problems related to the first solution in this paragraph.