No, at present BGT has no built in support for the screen reader APIs.
Personally, I think it is a bad idea anyway. Jaws, for example, has a
lot of problems with DirectX, causes DirectInput to lock up, etc and
any developer trying to use Jaws for speech output while providing
input via DirectX is just begging for trouble. Not only that even
though I know computers have better processors, more ram etc everytime
you run a TSR app like Jaws in the background it slows your system
down and uses up lots of resources that could go into a more advanced
audio environment or something. If you depend soully on the screen
reader for speech output you then have to factor those resources into
your over all system requirements etc. I just can't see using
Eloquence with Jaws is that much of an advantage here.
On 1/3/11, Kai <kaixi...@sbcglobal.net> wrote:
> Greetings list.
> anyone know if BGT has any provisions for interacting with the various
> screen reader API's? I would, for instance, like to replace a lot of the
> SAPI TTS events with direct Jaws speech output, since Eloquence is about 200
> times faster than SaPI.
> If not, anyone know if this will be slated for a future release?
> Gamers mailing list __ Gamers@audyssey.org
> If you want to leave the list, send E-mail to
> You can make changes or update your subscription via the web, at
> All messages are archived and can be searched and read at
> If you have any questions or concerns regarding the management of the list,
> please send E-mail to gamers-ow...@audyssey.org.
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.