KeywordManager keeps listening when inactive
See original GitHub issueThe current implementation of KeywordManager
starts listening for voice commands when the script’s Start
function is called. However, the underlying KeywordRecognizer
object is only stopped when the script is being destroyed - if the script (or any parent in the hierarchy) is deactivated, it keeps responding to voice commands (key bindings work correctly though, since these are processed in the Update
method).
KeywordManager
should check when it is deactivated and stop responding to voice commands until it is activated again.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How can I ensure Google never again incorrectly thinks my ...
By remaining signed in I would imagine the system might recognise my account as being active. Just please commit your password and email...
Read more >Is Google listening to me all the time via my Android ...
It is always listening to all your conversations. When you say OKAY Google, it activates the Voice search function. There is no way...
Read more >All the ways Slack (and your boss) tracks you and how to ...
While good password management and two-factor can help, it's also worth considering what you're sharing on Slack. Operational security is key – ...
Read more >Enable and disable standard commands for Voice Control ...
Voice Control listens only for selected commands. Disable a command: Deselect its checkbox. See alsoUse item number and grid overlays with Voice Control...
Read more >Take a last look at your unused Google accounts
Google's forthcoming content deletion policy for inactive accounts in Gmail and ... Google suggests users consider using a password manager ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello @HodgsonSDAS, I have just submitted a PR with the fix (#360) - not sure if it would be better than integrating it in @aalmada’s one.
@aalmada any chance you could address this in your PR?