I think speech interupt for typed characters should be checked by default.

[audiogamer22]

I came across a thread on applevis where the user was noticing a huge lag when using NVDA on the internet, the h key would take about 20 seconds to respond,, they finally figured out why, speech interupt was unticked, I tried unticking it and my god, the lag was so horrible.

So I'm proposing that it is either turned on by default or just removed and it being ticked is the default state of NVDA.

I bet someone tells me now, Brad/audiogamer, that's how it is anyway, if that's so I'll shut this down ASAP but if not, can someone explain why they'd want that feature off?

It just seams to make NVDA hang like crazy.

[CyrilleB79]

Hi @audiogamer22

"Speech interrupt for typed characters" is ticked by default in NVDA config so that's not a problem.

I have never unticked this checkbox and do not know any real life use case. I can just imagine some theoretical use cases, but never seen:

1. Disabling "caret moves review cursor" and "focus moves navigator object", and using "Speech on demand" mode, you can listen to a text read with the review cursor (numpadPlus) while writing in another document. But this setting is much older than speech on demand feature, so that could not have been the use case for this parameter.
2. Maybe in programs where letters trigger actions, you may want to perform action but keep NVDA speaking?

By the way, I realize that with "Speech interrupt for typed characters" disabled, letter or punctuation keys do not interrupt speech except when you press dead keys, e.g. using diacritics. This issue has never been reported probably because no one disables "Speech interrupt for typed characters" in real life...

[valiant8086]

By the way, I realize that with "Speech interrupt for typed characters" disabled, letter or punctuation keys do not interrupt speech except when you press dead keys, e.g. using diacritics. This issue has never been reported probably because no one disables "Speech interrupt for typed characters" in real life...

I use this feature. I have an NVDA profile for my mud client that turns speech interrupt for typed characters off but leaves it on for enter key. I don't use keyboard echo. In this way, I can type commands while I continue to hear incoming text in full, but when I push enter, it interrupts then so that what I will hear is the immediate response to the command I just typed. I would guess this is why the feature was added as it is a major benefit for this specific scenario. I see issue is already closed but worth documenting this one specific and valuable use case for the feature.

[CyrilleB79]

Thanks for the explanation of the use case @valiant8086. Very instructive.

[audiogamer22]

@CyrilleB79 Ah, ok, I'll close this then.