BT MPower 32 running Ks 7.5 build 29 (problem either never or not
significantly present on classic running ks 7.2)
When spacing between words, the bn will with some frequency combine
the space character with the last non-space character entered and
treat that combination as a chorded command. After the t-h-e sign
for the word "the", for example, I can easily find myself typing in
the format menu. When a word ends with the letter e, typing the
following space will exit the file. And so on. There are parts of
Keysoft which I probably would never have visited, except that an
unwanted chording of keystrokes intended as a character followed by a
space took me there.
The problem is worse the faster I type, which makes me think there's
a timing issue, or some feature of the hardware or software which
blurs the boundaries between characters being entered. If my typing
were just sloppy (which happens some times), I'd get the wrong
character, characters run together without a space in between, or
missing characters.
The problem is particularly bad when the last character of a word is
a braille contraction such as i-n-g, b-l-e, etc. After such
characters, I have to wait even longer than usual in order to prevent
the occurrence of an unwanted chording of that last character with
the following space. This means that typing has to be a bit choppy
and that I have to think more about the actual entry of the material
than I would have to without this problem. I imagine that the cause
of the problem in this situation is that Keysoft is back translating
on the fly and needs time to look up the symbol in some table, back
translate it then store the result before it's ready for more
input. If that's what's going on, I wonder if the problem couldn't
be fixed by buffering the translation process so that translation
could catch up with entry when, for example, I pause between
sentences or paragraphs. Alternatively, I'd like a way to turn off
the automatic back translation and, if it has to be done at all, let
it be done when the file is saved. If the file is to be a Grade II
file anyway, why back translate at all, unless told to do so through
the file-translate menu? If it's not back translation that's causing
the problem, what is it, and how do I fix it?
Hw tech support tells me the only thing I can do is to type more
slowly . But that approach makes me risk falling behind in meetings
or lectures. It also reduces overall productivity when drafting
documents from wat it could be if these problems did not exist. For
the price of the bn, and given its mission to enable braille users to
be productive in a medium which is hospitable to their skills,
features which slow down braile entry and which lose data when entry
is too fast seem particularly unwelcome.
Thanks in advance for any suggestions.
BTW: The problems described above happen both on battery and when
connected to power. The flash disk reports 56.9 mb free, so I'll be
surprised if overcrowding is the issue.
___
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
