Still looking for some prefix magic

[Kevin Hunt]

I want to have a command phrase for almost all of my commands.  However I also want the ability to disable the command phrase necessity for rapid fire commands.  I have a few solutions in mind:

1)  Make two seperate profiles, that are more or less the same but one has a global prefix listening override and the other does not.  Then my default profile has listening disabled with the override in place, and if I want to turn off the control word I say a command which changes profiles and enables listening.  This one is relatively simple but could have some problematic state changes.

2)  Another solution is to use condtional commands such as "[computer;] Engage thrusters"  Then I could say "Computer engage thrusters" or just "Engage thrusters".  I would then rely on an EXP function similar to this: "{EXP: '{CMD}' LIKE '{TXT:controlWord}*'}" to determine if the control word is said, and add on to the function some logic to determine if an override is in place.  This solution is ok, but the problem is every command now (and there could be hundreds) has to have hte command word manually entered, so changing the control word would take a lot of time, which would make it less mobile.

3)  The last solution would be to use suffix/prefix commands.  Have all of my normal commands as suffixes and hten have a single prefix command for the control word.  Then I would have "{EXP: '{PREFIX}' = '{TXT:controlWord}'}" to test if the control word is present.

Obviously solution 3 is the best solution because it allows me to make all of my command and then only edit two locations (the init file which specifiies the txt token controlWord, and the prefix command) to effect what the particular control word of choice would be for all commands.  

However there is a problem, currently there is no way to have a blank control word.  So there is no way to bake in an override because you can never "skip", so to speak, the prefix.  

Am I missing something here, or is this just a current limitation of the system?

[Kevin Hunt]

Anyone think they could lend a hand?

[Gary]

Are you saying you would want to always say something like, 'computer, fire weapons' and then just be able to say, 'fire weapons' when needed?

Gary

[Gary]

Also, most have migrated over to the VA forum:  http://www.voiceattack.com/forum (it's why its so quiet here).

On Tuesday, May 17, 2016 at 12:38:35 PM UTC-5, Kevin Hunt wrote:

[Kevin Hunt]

Yes, that is exactly what I want.  I want to have a prefix for my commands, but then if I am about to engage in a hectic situation, I want to be able to disable to prefix to allow for the commands to be spoken without the safety phrase.  

So ideally I'd have a command such as "fire missiles", and by default it would need the prefix "Computer".  So by default I would have to say "Computer fire missiles" for the command to activate.  However if I am going to go into a situation where time is of the essence I want to be able to say "Computer, disable safety phrase", and then all I would have to say is "Fire missiles" and the command would activate until I reactivate the safety phrase.

[wiesel]

The profile option 'Override listening if my spoken command begins with...' should be exactly, what you are looking for.
Activate this option and write the keyword you want to use into the field. Than deactivate the listening button in the main screen.
Now you can use the commands only by saying the keyword prior. To activate Listening option again, make a command named "Computer, disable safety phrase" and add the function 'Start VoiceAttack listening' (Other > VoiceAttack Action > Make VoiceAttack Start listening) into the sequence list and the Keyword isn't needed any more.

Let me know, if that works for you.

Wiesel

[Everton Harris]

Kevin,

The below link is what you are looking for.  Wells did a great job on this.

https://www.youtube.com/watch?v=XgbaIsxkJoI&index=2&list=PL_-EtZwLJtjqXCvsyra3TKCRPnywcYjhS

V/R

Everton