Quote:
Here's a hypothetical way I'd use it. I'd use it to further consolidate my Macros to specific devices/applications.
Global Prefix: Arthur
Macro: "Turn the Lights"
- IF: "ON" - execute lights_on.bat, TTS: "Lights powering on", exit macro
- IF: "OFF" - execute lights_off.bat, TTS: "Lights powering down", exit macro
- Else: TTS "I didn't understand"
"Arthur, turn the lights off."
(Macro matched - if [off] - executing lights_off.bat)
(TTS: Lights powering down now)
"Arthur, turn the lights NULL."
(Macro matched - else - TTS: I didn't understand, please try again)
Then I wouldn't need a separate macro for on, off, etc. A similar application would be a space simulator. You could do "arthur, shields up/down/etc" and consolidate macros into a single window.
I could also use the wait for logic (if implemented the way I'd imagine) to do verbal confirmation before exiting out of the macro. Some more complex macros might be inconsistent - and fail to complete one or two of several actions successfully.
In this case, I could have it execute my script to turn all of my theater devices on - and then prompt me for confirmation that it indeed worked.
Global Prefix: Arthur
Macro: "Turn the theater"
IF "ON" - Execute Theater_on.bat, TTS: "Powering on devices now. Did they all power up?"
Wait for: "Yes" or "No"
- IF "yes" - exit macro
- IF "no" - execute theater_on.bat
- ELSE - TTS: "Please respond with Yes or No"
IF "OFF" - Execute Theater_off.bat, "Powering off devices now. Did they all shut down?"
Wait for: "Yes" or "No"
- IF "yes" - exit macro
- IF "no" - execute Theater_off.bat
- ELSE - TTS: "Please respond with Yes or No"
ELSE: TTS "I didn't understand"
"Arthur, turn the the theater on."
(Macro matched - if [on] - executing theater_on.bat)
(TTS: Powering on devices now. Did they all power up?)
"Yes"
(Exit Macro)