Closed soundmud closed 8 years ago
If I remember correctly, when ScreenReaderAPI falls back to SAPI, the calls to speak or stop speaking can take around a second, making the UI uncomfortable. This problem doesn't appear when SAPI is used directly, if I remember correctly.
Commit ce033bdc00c8b6098e6497f295ecc6c4db0344cb fixes this issue by adding 2 threads.
If I remember correctly, when ScreenReaderAPI falls back to SAPI, the calls to speak or stop speaking can take around a second, making the UI uncomfortable. This problem doesn't appear when SAPI is used directly, if I remember correctly.