-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Give standalone users a "Shut Up" keybind #197
Comments
VA users actually have 3 commands that may be relevant here. One to shut EDDI up, one to disable the speech responder, and a third to enable the speech responder. If we take this route, we would probably want to make all three available for keybinding. |
I would settle for just the one that means "Shut up what you're saying right now". |
I wonder... would fleshing out the script priority system in EDDI accomplish the same purpose in your opinion? |
I don’t think it would. The |
The |
Good find. Let’s also ask the other EDCD folks for recommendations. |
I'd be happy with just a customisable keyboard input for a first iteration. We can look at DirectX later. |
Hello, Or maybe from a command line like EDDI.exe -shutup and just invoke that from AutoIT. |
At the moment, it is not possible to do this from either a hotkey or from the command line. The VoiceAttack plugin command directly invokes a method in the SpeechService class. EDDI/VoiceAttackResponder/VoiceAttackPlugin.cs Lines 872 to 886 in 79121eb
|
Could AutoIT be used to trigger this ? |
Not that I'm aware of (I don't use AutoIT). |
While VA users can say "Shut Up" to stop EDDI talking, standalone users have no such option.
Allow standalone users to configure a global keybind to invoke EDDI's
ShutUp()
function.Ideally users should be able to define two keybinds, and DirectX inputs such as HOTAS, game pads etc should be available as well as the keyboard.
NB don't make the mistake that Discord did: store the device as well as the button ID. Just because I bound button 9 on my stick doesn't mean that I want button 9 on my throttle bound too ;)
The text was updated successfully, but these errors were encountered: