Cool, nice to be right about something I don't even know about. smile
Sara
----- Original Message -----
From: "Jeff Bishop" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 30, 2008 9:28 PM
Subject: Re: Braille in scripting ...
You are correct.
----- Original Message -----
From: "Sara" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 30, 2008 7:07 PM
Subject: Re: Braille in scripting ...
Hi. I know nothing about programming but does this controlling different
sections mean that...
Say I have a 40-cell display. Could I use 20-cells for everything wineyes
and the other 20-cells only for a specific program's messages or
something.
Just being curious and don't really understand the technical stuff.
Sara
----- Original Message -----
From: "Ron Parker" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 30, 2008 8:51 AM
Subject: Re: Braille in scripting ...
A lot of this isn't documented very well yet because it isn't anything
like a final implementation in beta 1.
That said, freezing and unfreezing is like registering a hotkey. When
you call Freeze, it gives you back another Braille object that
represents your frozen chunk of the display. As long as you hold a
reference to that Braille object, your chunk remains frozen. When you
release that reference, it unfreezes automatically. In VBScript, you'd
do something like:
Set FrozenChunk = Braille.Freeze( bflRight, 10 )
FrozenChunk.Display(" a message")
' more code here, blah blah blah
SetFrozenChunk = Nothing
Freezing a chunk of the display automatically moves the unfrozen chunk
over so it can continue to behave normally, so if you freeze a chunk at
the left of the display you don't cover up the control type; it just
moves over so it's after the part of the display you now control.
In Beta 1, you can't freeze the entire display, and you may encounter a
debugging statement we accidentally left in the shipping version of the
code if you try. I'm not sure what that'll do if you don't have a
debugger installed, so I suggest not trying. I suspect that in the
future you will be able to freeze the entire display (and the debugging
statement is already removed for the next release, and the developer
responsible has been smacked around.)
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
