Jeff,
Right, if you change what is displayed on the braille display, when it
comes time for Window-Eyes to update what it thinks should be there it
will kill your text. So yes, if you want something to stay there in
tandem with the WE text you can free a section. If you want to take
over the total display then you could freeze the entire display.....or
at least the total unfrozen section.
To unfreeze a section, just lose the scope of your variable assigned to
the frozen section. WE takes care of the rest.
Doug
Jeff Bishop wrote:
Yeah, I got that far this weekend, but I sent a string to the display
and it got there but then disappeared rather quickly. Do I need to
freeze the display and if so how do I unfreeze?
----- Original Message -----
*From:* Doug Geoffray <mailto:[EMAIL PROTECTED]>
*To:* [email protected] <mailto:[email protected]>
*Sent:* Monday, June 30, 2008 6:06 AM
*Subject:* Re: Braille in scripting ...
Jeff,
You should look at BrailleDisplays.Active.Type
If this is 0 then there is no braille display. Anything other
than 0 you can look up the BrailleDisplayType enum to see what
display it is. You can also use:
BrailleDisplays.Active.Description to get the name as displayed in
the select braille display dialog. If they have no display
selected you'll get back "None".
Doug
Jeff Bishop wrote:
Hello GW,
To detect if a braille display is connected and active, do we
simply use the Application Braille property and insure it is not
nothing?
Jeff
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
