Re: nvda: its achievements over the years and its drawbacks
Hi keywasful
Well I can answer the first question simply enough.
Nvda needs to have a jaws intercept to use this extra function.
That would immediately stop it becoming portable though unless there is a way to load the intercept only when required.
The way intercepters work at least traditionally and this is before the xp direct chain manager, mirror drivers and uia at least from my experience is that say you have 3 readers hal jaws and windoweyes. or even 2 hal and jaws the first reader in the chain loads the next reader in the chain and that loads the next reader in the chain.
This loads the video card.
Yes, the traditional chains loaded in place of the video card.
The disadvantages of these were, uninstalling the readers in the wrong order would break the chain.
running by mistake both readers would break the chain.
running an old version of a reader and a new version would break the chain.
jaws got round that
somehow.
If that happened, 1 of 2 things would happen.
1. windows wouldn't load the video card and then not boot.
2. the video would load in basic mode.
The chains are created by an entry in the gdichain.ini found in the windows system folder and a modification to the registry which I got someone at dolphin support to create ffor me.
you need to know your interceptor ids and names and video driver names.
In the second case I was able to reinstall the video drivers and reinstall one of the reader's intercepts and have speech but that was it there were redundant entries in the chain and I was not able to fix those.
To fix it fully reformat and reinstall and the problem would go away as it always did till you broke the chain which as you can imagine was quite easy to do I reformatted every week or sometimes every day because I would run 2 readers at once by mistake.
Direct chain manager cured this ms and gw worked on it and
it basically was a library standard that would stop this.
The library was the chain link there was still a chain but now all readers linked the library to their drivvers and that linked the video card.
When vista came in though user account control and other things basically made the direct link impossible so a mirror driver was used to pull everything together and this fixed things for now.
In win8 and up ms decided to scrap ms active access msaa and morf all their access to user interface automation or uia.
Uia is an access library which runs in 7 and 8 with a broken version optional in xp maybe vista has uia.
In theory therefore all readers run under uia now and starting with supernova 12, everything ran off uia.
So saying that I guess its possible for nvda to have an intercept, just like other libraries it interfaces with for access it has full interface to uia but its not enough.
any nonstandard controls are still not read its why I have super
nova screen reader loaded on here to.
As for frontends I am not sure how that would work for nvda, the closest we could get would be an ide for python but who knows.
there are consoles you can input sertain scripts into and make once only changes to the current runtime, nvda is built on a dll compiled python 2.7 executable so in theory you can tell it things but you can't keep it.
One strength of nvda over others is it can call programs, not just scripts to help it understand things but programs like free ocr engines and other things.
speech synths and the like and other things.
it can call sertain libraries in c++ to apparently and espeak voices can be made and installed in the right folders.
One thing nvda has is the controller client which basically tells nvda what to do.
I know jaws and dolphin stuff have apis to handle this but the nvvda controller basically instructs nvda what to do and how things should be read.
So you could in the
ory make programs nvda ready either with scripts or as a program author including nvda libraries in your code and tell nvda what to do.
However what you need to remember is that nvda is an opensource package and while its had a few grants for a few of its libraries, most of what it uses from its ocr to some of its synths and braille drivers and libs are in fact opensource projects most of these were created for Linux origionally and were either ported to windows or spacifficly created for the project.
With all that said there are vary few programs nvda doesn't work with per say.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
