Hi,
Ah, I see. Then I think you and other geeks should ask HW for a
driver update to support this new IP standard - which means
fundamental change on how we read IP addresses...
As I said before, with your knowledge, I'm sure HW would love to
have you as a "beta tester" later.
Cheers,
Joseph
----- Original Message -----
From: Sabahattin Gucukoglu <[email protected]
To: [email protected]
Date sent: Fri, 11 Feb 2011 20:49:52 +0000
Subject: Re: [Braillenote] Surprise, It's The Email On File,and
brltty BrailleNote Driver Breaks
On 11 Feb 2011, at 12:41, Joseph Lee wrote:
What other things have you discovered? How about stability
against 9.0?
I'll have to wait a bit longer to see if it locks up. Certainly
though, it's getting less use in the braille terminal, obviously,
and that might have something to do with it. I'll say that it is
much snappier in other applications, though, like the web (still
don't dare to trust it with my mail, just yet, maybe when I've
moved my inbox messages elsewhere).
For the other stuff, let's see ... Ethernet works by creating a
default DHCP connection, which conflicted with my old one.
Removed my old one, without effect, but it does mean you can
clobber the feature by just removing the default one. And of
course if you use a static configuration, it doesn't fall over to
another connection when DHCP isn't available - it just puts up
the standard Windows CE error.
In the QT edition, while in the braille terminal, you get
spurious options for the scroll wheel, and no way of knowing
about the Function+I keystroke. And as always, the documentation
reader is slightly off. There were occasions where turning off
braille wouldn't really turn braille off; it would either leave
the dots in their current position, or blank the display, but
never physically turn it off. And the "Text-to-speech
improvements" include pronouncing QT as "Quartz", which means my
device is called the BrailleNote Apex Quartz (ah, go on, that can
hardly be described a bug). No, IPv6 wasn't there, so I guess it
hasn't made it to their radar screens.
Just silly little things, nothing serious, except the braille -
that is a tragedy. Braille without input is like chocolate
without hazel nuts. And brltty was way, way ahead of many screen
readers in braille input capability even when HumanWare did not
directly support it. The entire input functionality was done
using layered commands, press a combination to enter input mode
and your braille keystrokes turn into their equivalent characters
when typed. Press another key to go into navigational mode. To
enter combinations including dots 7 or 8 or both 7 and 8, just
press another layered command, and either just the next key, or
all subsequent keys, have those dots added.
Cheers,
Sabahattin
___
Replies to this message will go directly to the sender.
If your reply would be useful to the list, please send a
copy to the list as well.
To leave the BrailleNote list, send a blank message to
[email protected]
To view the list archives or change your preferences, visit
http://list.humanware.com/mailman/listinfo/braillenote
___
Replies to this message will go directly to the sender.
If your reply would be useful to the list, please send a
copy to the list as well.
To leave the BrailleNote list, send a blank message to
[email protected]
To view the list archives or change your preferences, visit
http://list.humanware.com/mailman/listinfo/braillenote
