A 32 cell display will give you a physical cell count of 32.
Aaron
Jeff Bishop wrote:
OK, is the cell count from the property 0 or 1 based and if one I can
simply get the count and subtract one from it... I will implement
something shortly.
----- Original Message ----- From: "Doug Geoffray" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 30, 2008 7:01 AM
Subject: Re: Braille in scripting ...
Jeff,
Sounds like you want an excuse to put this off <smile>. I suggest you
just freeze all but one cell so you can at least proceed. Then when
we finalize all this can I get done kicking around the developers you
can remove the -1 part of the freeze.
I really would value feedback if there are issues as now is the time
to fix it not after 7.0 ships <smile>.
Doug
Jeff Bishop wrote:
OK, excellent Ron. Marlaina has asked that I add braille support for
the Winamp scripts. I will wait then until the next public beta.
----- Original Message ----- From: "Ron Parker" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 30, 2008 6: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
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
