Re: Empirically setting a screen reader delay
Thanks everyone for your suggestions. It seems like some of you have gotten it to work reliably for determining if a screen reader is speaking, though I'm getting pretty accurate timings with the solution I've currently got, especially once I wrote a function to convert numbers to words which was the biggest problem I was facing since one number like 1600 counts as one word unless it's explicitly converted into words. Of course now the issue is localization since I'm only accounting for English number to word conversions. Any ideas on this part? I've been unable to find a C# number to word conversion library and don't want to bother with writing my own complex localization code if there's a library out there that already does this.
The main reason I don't think I'll be using snvol is because of the purposeful delay to check if the screen-reader is still speaking. It smells of race conditions as in this example:
1. Check the volume.
2. If it's 0, assume the screen-reader has just paused and wait 500 MS.
3. If the volume is above 0, go to step 1.
4. If not, the screen-reader is finished speaking.
Assume here that after your 500 MS delay you happen to check the volume while the screen-reader has taken another pause. You will incorrectly determine that the screen-reader is finished speaking.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
