problem with double letters and brailleInput sendChars #4139

Closed
nvaccessAuto opened this Issue May 11, 2014 · 3 comments

2 participants

@nvaccessAuto

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.resultsindex 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.

@nvaccessAuto

Comment 1 by Michael Curran <mick@... on 2015-01-30 03:59
In [b903c75]:
```CommitTicketReference repository="" revision="b903c757e1ad4913d4faae9ed349f68634225f57"
Merge branch 't4139' into next. Incubates #4139

Changes:
Added labels: incubating
@nvaccessAuto

Comment 2 by Michael Curran <mick@... on 2015-03-16 05:44
In [cc8ee66]:
```CommitTicketReference repository="" revision="cc8ee663033161707a02ac0c369a143e332cfb46"
Merge branch 't4139'. Fixes #4139

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto

Comment 3 by mdcurran on 2015-03-16 22:37
Changes:
Milestone changed from None to 2015.2

@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2015.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment