Profile command to autorun before every recognized voice command

[FlyingFree]

Being able to designate an action, like making a beep sound, following the successful recognition of a voice command, before executing the actions associated with that voice command, would allow a simple feedback mechanism to let users know the command was heard and recognized. This is especially useful for voice commands that have no visual or auditory component so lacking feedback it's hard to tell if the command was executed. Of course you can add a beep sound to each command but that is tedious, especially if you need to change the sound after creating dozens of commands. Possibly also add in an opt-out checkbox for commands to not trigger this behaviour for situations where you may have 1 or 2 commands you want to run silently.

[Gary]

This was a design discussion early on.  As simple as that would be to implement, along with most global settings, 'global' is great right up until the time you don't want it to be (even if, 'global' is at the profile level).  When something is global like that, you have to *constantly* create interfaces for exceptions.  You've already hit upon a couple of them... Some would want the action to be performed BEFORE the actual command and not after.  Some would want to exclude certain commands, some would want it to run asynchronously and others synchronously.  Some would want a particular sound in particular instances.  It just goes on and on.  So, in this case, the onus is on the user to make that happen.  What you'll want to do is first create a command that plays a sound.  Then, create a dummy command with an, 'execute other command' at the top that executes that sound.  Instead of hitting, 'New Command', you just duplicate the dummy command.  Since the sound is in it's own command, you can change it in one place and it will be changed everywhere.

Hope that helps!