Author Topic: Enqueue command instead of immediately executing  (Read 383 times)

WillRiker2701

  • Newbie
  • *
  • Posts: 19
Enqueue command instead of immediately executing
« on: February 24, 2025, 04:34:35 PM »
Hi, I would like to know if it would be possible to add the option to enqueue the command to a specific queue instead of immediately executing when saying the trigger phrase.
I know this can be done by using two commands, one that enqueues and the other that contains the algorithm to be executed, but I'm currently working with profiles that have hundreds of commands, and duplicating the amount of commands sounds very inconvenient if there's an alternative to just enqueue them directly when being called.
It would be a great addition.

Cheers!

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2845
Re: Enqueue command instead of immediately executing
« Reply #1 on: February 24, 2025, 06:36:22 PM »
Hi, WillRiker2701 -

What you probably want to use are command queues.  Hit F1 while VoiceAttack is in focus to bring up the help doc - search for 'Command Execution Queues Overview' to bring up the overview (or 'Command Queues' to bring up other instances).

Hope that helps!

WillRiker2701

  • Newbie
  • *
  • Posts: 19
Re: Enqueue command instead of immediately executing
« Reply #2 on: February 24, 2025, 07:29:15 PM »
Hi, thanks for your answer.

I know about the current queue mechanics in VoiceAttack, but what I'm suggesting is something that is not currently possible to do (as far as I know by what the manual describes).
As of this moment the only way to enqueue a command is to use the 'Enqueue a Command' action by clicking, Other > VoiceAttack Action > Command Queues > Enqueue a Command. This action is of course included within a command that requires to be executed. So we need to create 2 commands: One that contains the "Enqueue a command" action, and a second command that is the actual command to be enqueued.

What I suggest, is that enqueuing commands is made possible directly by a voice "order" instead of requiring to use the "Enqueue a command" action within another command. In other words, to not require the existence of 2 commands for it but only 1. When I say "Gear up" for example, that the command to raise the landing gear does not immediately execute, but that it enqueues to be executed when other commands in that queue finish their sequence. Enqueue (instead of execute) by voice command.

I hope I made myself clear about what I mean, and please tell me if I misunderstood something regarding the queue mechanics.

Thanks!

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2845
Re: Enqueue command instead of immediately executing
« Reply #3 on: February 24, 2025, 07:52:30 PM »
Sorry - long day.  I misread what you were saying initially.

If I'm reading this right, you would want to just have a command option that says, 'Enque to 'some queue' - the command is then placed in that queue rather than being executed immediately.  The queue itself can just be in whatever state its in - doesn't matter to the command.

I'll add this to the research list.

WillRiker2701

  • Newbie
  • *
  • Posts: 19
Re: Enqueue command instead of immediately executing
« Reply #4 on: February 24, 2025, 08:06:08 PM »
Exactly, like for example when creating a new command instead of having "This command is executed: When I say ..." to have the option to set it to "This command is enqueued to queue 'enter queue name': When I say ..."
Or maybe another way but to achieve the same purpose.

Thank you! Cheers.