Windows 10 - Talon Version: 0.2.0-357-g3b3e
This is something that came up during Talon HUD development, specifically for the following flow:
- Bring up choice widget with 'toolkit options'
- Close the choice widget by saying 'dismiss toolkit'
- Reopen the choice window again by saying 'toolkit options'
- Now the 'dismiss toolkit' voice command no longer seems to work.
What is happening in these steps is the following:
The list containing voice commands connected to choices is updated with the available choices so that they can be activated by voice. Once the choice widget is dismissed, this list is set to an empty object. When reopening again, the list is filled with all the available choices again, which are the exact same options as in the first step. I can confirm that the choices are set with a different object, but the contents are the same.
I have tested this with an empty list as well, as well as transforming the list connection in the .talon file to a capture instead. In all of these scenario's, the exact same result is achieved: The voice commands for those choices are no longer available.
I can avoid this by not setting the choices list as an empty object or list, but instead provide a single entry with a bogus voice command that does not activate anything. In this case the voice commands seem to properly activate if I repeat the steps shown above.
The HUD specifically keeps a few lists empty if there are no options available to be activated, as is the case if there is no right click menu open, or if there are no choice buttons available to activate.
Windows 10 - Talon Version: 0.2.0-357-g3b3e
This is something that came up during Talon HUD development, specifically for the following flow:
What is happening in these steps is the following:
The list containing voice commands connected to choices is updated with the available choices so that they can be activated by voice. Once the choice widget is dismissed, this list is set to an empty object. When reopening again, the list is filled with all the available choices again, which are the exact same options as in the first step. I can confirm that the choices are set with a different object, but the contents are the same.
I have tested this with an empty list as well, as well as transforming the list connection in the .talon file to a capture instead. In all of these scenario's, the exact same result is achieved: The voice commands for those choices are no longer available.
I can avoid this by not setting the choices list as an empty object or list, but instead provide a single entry with a bogus voice command that does not activate anything. In this case the voice commands seem to properly activate if I repeat the steps shown above.
The HUD specifically keeps a few lists empty if there are no options available to be activated, as is the case if there is no right click menu open, or if there are no choice buttons available to activate.