You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by ABuffEr on 2014-05-11 20:01
Hi,
testing the addon GoogleSpeechRecognition, I and others found that, in some applications (wordpad, notepad++ in my test), using this code:
for mychar in self.results[string written presents generally only one of double letters; so, "stopping" becomes "stoping". It not happens in notepad and NVDA console, for example. Obviously, the string self.results[index](index]:
brailleInput.handler.sendChars%28mychar%29
the) is correct.
I tested on Windows 7 64-bit, but some months ago I noticed this behaviour also on XP, so probably it's Windows version independent.
I tested also setting no Braille display, disconnecting it and restart NVDA; and, I verified, filter keys on keyboard settings in control panel is disabled on my system.
The text was updated successfully, but these errors were encountered:
Reported by ABuffEr on 2014-05-11 20:01
Hi,
testing the addon GoogleSpeechRecognition, I and others found that, in some applications (wordpad, notepad++ in my test), using this code:
for mychar in self.results[string written presents generally only one of double letters; so, "stopping" becomes "stoping". It not happens in notepad and NVDA console, for example. Obviously, the string self.results[index](index]:
brailleInput.handler.sendChars%28mychar%29
the) is correct.
I tested on Windows 7 64-bit, but some months ago I noticed this behaviour also on XP, so probably it's Windows version independent.
I tested also setting no Braille display, disconnecting it and restart NVDA; and, I verified, filter keys on keyboard settings in control panel is disabled on my system.
The text was updated successfully, but these errors were encountered: