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

Value of sliders in the voice settings dialog is not always reported when changed #1411

Closed
nvaccessAuto opened this issue Mar 10, 2011 · 4 comments

Comments

@nvaccessAuto
Copy link

Reported by aleksey_s on 2011-03-10 13:13
STR:

  • open the voice settings dialog (NVDA+control+v)
  • Navigate to the rate slider
  • press up arrow several times
    Actual results:
    Sometimes, NVDA doesn't announce slider's value.
    Expected results:
    NVDA should always announce the value.
    Additional info:
    The text about the change isn't passed to the synthesizer.
@nvaccessAuto
Copy link
Author

Comment 1 by KevanGC on 2011-03-11 06:56
I have the same problem with all the other sliders in the dialog. It works when pressing left and right arrows but does not when pressing up and down.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2011-03-11 07:08
Most likely a regression caused by fd1c265 (fix for #221). If I'm right, this means that this would have worked fine in 2010.2. It'd be great if someone could verify this.

It doesn't affect left and right arrows because they pass the event through normally and don't use this code. It looks like posting the event manually is not enough to make it behave normally.
Changes:
Milestone changed from None to near-term

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2011-06-14 22:46
Changes:
Changed title from "rate slider's value in the voice settings dialog is not always reported when changed" to "Value of sliders in the voice settings dialog is not always reported when changed"

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2011-06-15 05:14
c107a8d
Changes:
Milestone changed from near-term to 2011.2
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

1 participant