Check to see if command is already running

[Woofington]

So I know I can stop another command from executing within a command, but I want to ensure the command I am calling, was not called previously as there is some pauses in the command so it could be double invoked.  However using the "stop executing command" on itself means it will never actually perform any if it is running, I instead want to cancel the first invocation of the command but keep the second one running.  Any ideas how to achieve this?

[Rhaedas]

Take your current command in question and rename it as a subroutine. Then use the command name that starts the operation first kill any of the subroutine name running, then call it.

As an example, here's a part of my routine for engaging warp. I only wanted one instance of a scanner reset run at a time.

Code: [Select]

Kill command, 'reset scanner'
Execute command, 'reset scanner'

This way the kill doesn't kill itself, like you mention, just that part that you want.

[Pfeil]

Take your current command in question and rename it as a subroutine.

That's better than what I was going to suggest, which was to have the command check whether it was running, and if so to call another command to kill the first command and restart it.

Nice one.

[Woofington]

Thank you, I have a follow up question.



question, is there an easy way to make a command that is run anytime a phrase is recognized other than injecting it into each and every command?

[Rhaedas]

Under editing commands, there's a checkbox beside the profile name at the top. That's your profile options. Click on it, and in those options there's one to always execute a certain command when any phrase is recognized.

[Pfeil]

there's one to always execute a certain command when any phrase is recognized.

That's for dictation phrases only. There have been requests to have an option that works with commands, but it has not been implemented(yet?) as far as I'm aware.

So no, there is no easy way, currently.

Belay that. There is a way without adding something to every command, however it is something of a kludge:

Code: [Select]

Set Text [LastCMD] to ''
Start Loop While : [{PROFILE}] Equals '{PROFILE}'
    Begin Text Compare : [{LASTSPOKENCMD}] Does Not Equal '{CMD}'
        Begin Text Compare : [{LASTSPOKENCMD}] Does Not Equal [LastCMD]
            Set Text [LastCMD] to '{LASTSPOKENCMD}'
            Write '[Purple] Trig'd' to log
        End Condition
    End Condition
End Loop

Now, this has drawbacks, as you'd expect. Majorly, it will only work if the command spoken after another command is different. Additionally, because it's a loop within a command, it will stop running when you open the command list.

[Rhaedas]

My mistake, I don't use any of those on that screen, just thought that's what it would do. If it's just dictation being recognized, as good as Windows is with that, that command would rarely get triggered.