![]() |
Show 20 posts from this thread on one page |
VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Visor Prism (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=19)
-- Prism Grafitti Recognition Problem--Handspring's Response (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=9123)
Sometimes it pays to go to the top. I just received a reply from a Handspring Executive to an email I sent yesterday regarding the many posts here on VisorCentrial concerning graffiti recognition problems with the Prism.
First, here is my email:
quote:
I'm a proud owner of 3 Visor Deluxes and am ready to purchase a Prism. However I do have a concern. There are many owners of the Prism that have posted problems on VisorCentral.com concerning terrible Grafitti recognition.
http://discussion.visorcentral.com/...p?threadid=8912
The problem has been so bad that many of them have had to return their Prisms for a replacement and the replacement has the same problem. (Some are even on their 3rd replacement.) So this doesn't seem like an isolated incidence. Is Handspring aware of this problem? Is this a design flaw or possibly a bad batch of first-run Prisms?
When spending $449 on your top of the line product, I want to be confident my unit will operate properly. I will anxiously await your response on this issue.
quote:
We have seen a few units with this problem, which is caused by noise generated by the display. It's a bit early to tell the magnitude of the problem - most displays don't exhibit the problem at all and, in fact, it has been hard to get units that show the problem in order to debug them. Whatever the extent of the problem, we do have a warranty on the product, and we will replace any units that don't work correctly.
I've already received a replacement because my first Prism had the problem you are all talking about.
That replacement Visor is almost just as bad. Graffiti is a little more accurate, but the top portion of the screens sucks as bad as the first one.
I am now waiting for a third Prism and am half expecting this one to be as bad as the first two.
My graffiti has improve over time (especially at the edges of the screen). Wait a week and see if it clears up on its own. My prism's recognition now is 99% of what my deluxe was (finally!).
__________________
-Joshua
Abortion: Darwinism at its finest.
I've been closely monitoring this problem on both Prisms, and the problem does not diminish in any way.
I don't have this problem on my Prism, but has anybody tried the AutoDigi or OnDigi hack? According to Palmgear, it records your digitization settings, and resets it to these settings everytime you reset (with AutoDigi), or everytime you turn the Palm device on (with OnDigi). It looks like OnDigi is a plug in for AutoDigi.
Again, I don't have this problem, but you might want to give this a shot, instead of sending the unit back.
-Just a though
And, no, I have nothing to do with either of these companies who produce these apps.
Thanks for the suggestion. But the problem here is bad digitizers/screens. It isn't that the digitizer settings are being improperly reset or erased over time, which is what OnDigi or AutoDigi my resolve, but that the screen completely misregisters taps. Mind you, it's only by no more than 4-10 mm, but these distances are major when talking about pixel-point tapping accuracy. So even the prospect of manually digitizing is very frustrating, especially since you cannot see what the screen is registering when you digitize. You have to open up applications, tap randomly across the screen and see whether the you're accurately registered.
I feel the same way dtgillis feels: if I'm paying $450 for this thing, a major component (the screen) ought to be at least functionally flawless.
Just got my Prism today... Actually arrived a day before
I thought it would...
Grafitti is a problem here as well.
Using TealEcho which shows the stokes as you make them, you can see where the computer is messing up. What I am drawing is not being represented properly and it is not just it being off a bit, but rather it appears to be
skipping. Making straight lines accros when I actual made
a curve.
Comparing the two side by side, I find that I can do repeative characters like x over and over on the DLX
20, 30 in a row without a single error. On the Prism,
after 20 attempts, I ended up with FxxotxxtxoxF
That is 12 total character out of 20. How does an F
stroke look like an x stoke?
It is obvious when looking at the output even in the Grafitti learning screen which also shows you what you are entering, that the digitizer is truly messed up. The stokes being recorded are not fluid, almost like the unit can't keep up with the input.
Will have to call in the morning to report the problem...
__________________
Kevin Reed
TNET Services
<IMG src=http://www.tnet.com/images/flag_az.gif>
| All times are GMT. The time now is 01:00 AM. | Show 20 posts from this thread on one page |
Powered by: vBulletin Version 2.3.4
Copyright © Jelsoft Enterprises Limited 2000 - 2016.