Give standalone users a "Shut Up" keybind

[richardbuckle]

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 ;)

[Tkael]

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.

[richardbuckle]

I would settle for just the one that means "Shut up what you're saying right now".

[Tkael]

I wonder... would fleshing out the script priority system in EDDI accomplish the same purpose in your opinion?

[richardbuckle]

I don’t think it would. The ShupUp() function interrupts EDDI mid-sentence which is not quite the same thing.

[Tkael]

The SharpDX library (or similar) looks like it will be needed for DirectX inputs. http://sharpdx.org/

[richardbuckle]

Good find. Let’s also ask the other EDCD folks for recommendations.