Skip to content
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

Speaking of spelling continues later if interrupted #1188

Closed
nvaccessAuto opened this issue Nov 8, 2010 · 3 comments
Closed

Speaking of spelling continues later if interrupted #1188

nvaccessAuto opened this issue Nov 8, 2010 · 3 comments

Comments

@nvaccessAuto
Copy link

Reported by RamboUdin on 2010-11-08 03:59
STR:

  1. Open winamp and load a track.
  2. Using the NVDA latest snapshot, press insert+t twice quickly, and hold the insert key for about 4 seconds while NVDA is spelling it.
  3. Listen to the spelling. Sometimes, NVDA will do it right, but sometimes NVDA will spell wrong things. (cannot understand what NVDA spells)
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-11-08 21:55
I don't understand the issue. Please set your log level to input/output in NVDA menu -> Preferences -> General settings, reproduce the issue and then attach the log file to this ticket.
Changes:
Milestone changed from None to None

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2010-11-10 16:50
Correct str:

  1. Press NVDA+t twice.
  2. Before NVDA finishes spelling, press any key to stop it.
  3. Now press NVDA+t twice again.
    The remaining characters from step 1 will be mixed among the characters from step 3.

This is because globalVars.keyCounter doesn't get set anymore since inputFramework got merged. However, relying on this is fairly dodgy anyway. Instead, speaking of spelling should be completely cancelled whenever speech is cancelled.
Changes:
Changed title from "Spelling titles in windows (especially in Winamp) causes problems to NVDA" to "Speaking of spelling continues later if interrupted"
Milestone changed from None to 2011.1

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2010-11-10 16:53
Fixed in 7a72bd3.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants