When to use built-in Dragon functionality

Dragonfly is so powerful that it’s easy to forget that Dragon does some things well out-of-the-box. To maximize your efficiency, it’s important know when it’s not worth it to reinvent the wheel. In this post, I’ll describe when I prefer to use built-in Dragon functionality.

Dragon’s strength is natural language dictation and editing. It allows you to speak continuously for any length of time, and it’s very convenient to correct words and move the cursor by referring to previously dictated text. But as soon as a Dragonfly command is uttered in an unsupported text field, Dragon will no longer let you make corrections. So when dictating English text, I generally try to avoid using Dragonfly commands. If I want to dictate variable or function names from code, I just use “cap”, “no caps”, and “no space” to help. This way I can keep dictating without any pauses. I will occasionally switch to Dragonfly commands when making small corrections, but I try to avoid it. When possible, I try to use the built-in “correct …” commands, and when that is not sufficient I use “go back” after making an edit to quickly jump back to where I was.

Whether dictating text or code, I prefer to add misrecognized words directly to the Dragon vocabulary instead of putting these into my custom grammar. This makes it easy to train the words, and I have designed my grammar so that it works in harmony with the Dragon vocabulary. For instance, if I have a common class name “SimDataManager”, I would add the phrase “sim data manager” to my vocabulary and then I can easily style it with underscores or camel case using my Dragonfly commands, without having to treat it as a special case. Similarly, if I have a frequently misrecognized command that I don’t want to change, I will train it using Dragon, taking care to not add it to the vocabulary (using “train word”), which would create ambiguity between command and dictation.

I recommend familiarizing yourself with the Dragon Command Browser (“open Command Browser”) so you know what is available. Note that the “Show all” button is helpful for expanding ellipses in commands. Some of my favorite short commands are “display text” to open the dictation box, “edit all” to select all and open the dictation box, and “edit words” to open the Vocabulary Editor.

When do you prefer to use built-in Dragon functionality to custom commands? Please post in the comments!

P.S. I would like to acknowledge the help of Mark, one of my readers/commentors, who influenced me on this subject and pointed me to some of the most useful built-in commands.

8 thoughts on “When to use built-in Dragon functionality”

    1. I would separate apps into three categories: (1) those with full text support, (2) those that support Select-and-Say if not mixed with other commands, and (3) those that break even with the most basic Select-and-Say usage. Unfortunately Emacs, my primary editor, falls into the third category. Sometimes Select-and-Say works, sometimes it doesn’t (e.g. it doesn’t modify the correct segment of text). When I use it over NX, even “scratch that” doesn’t work properly. Fortunately, I don’t do a lot of natural language editing in Emacs. I might if this worked, though.

      The main place I do natural language editing is within Chrome, such as when writing emails. I find that the built-in Dragon support for Chrome is really buggy and frequently causes hangs, so I disable it. That effectively changes chrome from a (1) to a (2). When I am working on a long piece of text, I will open the dictation box. For some reason the dictation box is slow to start, so I am planning to try to set this up with a faster editor with full text support (e.g. Notepad).

      1. I believe Outlook has full Select-and-Say support, and it supports most of the built-in Dragon commands for formatting text. I don’t use it myself, but I believe Dragon is about as powerful in Outlook as it is in Microsoft Word.

  1. Some of the built-in Dragon commands for PowerPoint are hard to duplicate by keystrokes. For example, slide 1 or object 1.

    1. It should improve everything. It gives Dragon three kinds of information:

      Which words you tend to use next to one another (this improves context recognition when dictating). This won’t help with commands.
      How you pronounce the individual words in the document. This will only help if you have your commands in the doc.
      How you pronounce individual phonemes (i.e. your accent, voice texture, etc.). This one will improve command recognition.

Leave a Reply

Your email address will not be published. Required fields are marked *

Markdown is supported. Make sure raw < and > are wrapped in code blocks. You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>