Hi folks, particularly HumanWare staff and programmers,
Thanks to a list member, I figured out at least a pattern to a
bug in Find and Replace. Based on my experiments, it appears to
be a logic error with programming (odd calculations or somewhat
odd behavior when a program is run but appears to be fine (at the
first glance) to the programmer). Here's the pattern:
* Find and Replace will work with words that are separated by
space characters.
* Find and Replace will not work if a string that you want to
replace is a part of a word e.g. If we want to replace
BrailleNote with BrailleComputer (replaacing Note with Computer),
it will not work as expected. KeyWord says, "cannot find string"
where "string" is the part of a word we are looking for.
* Find and Replace will lock your unit (at least on your Apex) if
the search string is surrsh^ed by or next to a punctuation
character e.g. If the string "BrailleNote" is enclosed by
parentheses, it will not work. This happens if the search string
is enclosed by a punctuation on one or both sides of the string
that you are looking for. In reality, KeyWord still runs (I have
confirmed this when using speech), just that it will not respond
to anything except resetting it (this is called "infinite loop").
* Also, sorry to tell you (Zach), that it IS a problem with
software. Suppose if this only occurs with certain document
types; then whatever the formatting of the document is to blame;
suppose if it happens with certain words; then we can avoid using
those words. Since this problem occurs on ALL document types
with the conditions outlined above, it is a logic error with the
software code (if my guess is right; I had to figure out a
similar error with date calculation when I did that assignment).
If you want to experiment with it, try it on a document that has
all the conditions as described as above (words with spaces,
words with punctuation next to it, and try it with speech turned
on, as it will give you a clue that it is an infinite loop).
Well, hope this gives you a broad picture here. I hope this
would be solved soon.
Cheers,
Joseph S. Lee
University of California, Riverside
___
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
