With your code, if I load up a Python REPL and set percentage = 1, I
get 110. If I set it to 100, I get 3957.
This exacerbates the issue. I don't know what 3957 Hz sounds like,
but I do know what middle C and an octave above that sounds like.
Imagine if progress bars were some weird random size, and a sighted
person had to look at them and guess how far along progress was.
They don't have arbitrary values, but fixed borders along which
progress moves. I don't care whether we have one octave or 2,
whether it's A-A, C-C, A#-A#. But I do think we need tones with
known bounds that we can easily conceptualize.
Anyhow, I'll attach this patch to the bug report soon. Having some
internet issues here and web use is painful ATM.
On 02/17/2016 01:31 PM, chrys87 wrote:
Howdy,
i tried your patch. i didnt recognize a big difference in the
beginning...
try the attached one (test.py)
now it works this way
return( int(100 + percentage * (percentage / 3.5 + 10 )))
cheers chrys
Am 17.02.2016 um 19:20 schrieb Nolan Darilek:
Hey,
So I had some of the same issues with progress bar beeps that I
did with NVDA. As an experiment, I whipped up this patch.
Basically, according to my non-coffee-fueled back-of-napkin
calculations, the current implementation starts progress bar
beeps at a few hundred Hz and scales them up to something like
2100. I don't objectively know what 2.1 KHz sounds like, but I
do have some objective notion of what an octave sounds like, and
just as a sighted person doesn't have to think about how far
along a progress bar is, I think we should have the same
convenience.
This patch starts progress bar beeps at middle C and ramps the
progression up an octave linearly. I initially had a logarithmic
implementation but found it more confusing than I thought.
Perceptually the progress bar appeared to move quickly then slow
down, which is consistent with the numbers. I haven't tested
this out with faster progress bars yet so there may be some
benefit to logarithmic, but one thing at a time.
We may also be able to drop the volume-scaling code if we're not
ramping the frequencies up above 1 KHz, but I haven't tested
that yet.
Thoughts?
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org
|
