Re: Questions on BGT
I don't know if it's able with VoiceOver, I never developed under OS X, but all screen readers don't implement such functions as it seems. That could be to the simple reasons that sapi developed it's own way of implementing synthesizers, which people used to build the sapi 5 voices we now use and had to have functions defined in a specification by Microsoft. Screen Readers like NVDA use several synthesizers and drivers who were developed by several other companies who all defined their own specification. Even if the Vocalizer voices in NVDA would support detecting if they're currently speaking or not, it won't be guaranteed that Eloquence supports this feature. Or eSpeak. And so on. That's probably the problem. NVDA depends on several third-party products, while Microsoft forced the developers to adapt their specification, which means that all voices assembled under SAPI need to return if they're currently speaking or not, making it possible
to implement a speak_wait method. Other products don't have to support this feature, that's why screen readers don't expect them to exist and don't implement such a function. Anyway, i'm not sure about it, but that could be some reason.
Best Regards.
Hijacker
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
