For some reason, I'm having a really hard time getting
my Visor Prism calibrated nicely for QuickType (I've had
it working nicely in the past, but a recent crash has
forced me to reinstall all apps).
In particular, my graffiti area seems to be somewhat non-
linear when I try to define keystroke areas. For
example, if I get keys near the middle of the keyboard
mapped correctly, keys near the sides don't seem to be
lined up correctly. If I correct for the sides, the middle
keys are off again.
If I'm fighting some kind of hardware bug on my
particular platform, it might make sense for me to be
able to define precisely the left, right, top, and bottom of
each key in terms of the coordinates. From my quick
perusal of the source code, it looks like the coordinates
of each keyboard location are stored in a data
structure. I'd just like a way to load that data structure
myself instead of just defining key width and height, and
letting quicktype assume a linear key arrangement.
Another feature that might be helpful in diagnosing this
kind of thing would be some kind of hook into the guts of
quicktype that would allow me to see the coordinates of
each tap and what quicktype discerns it as.
Thanks again for a cool product.
Rick Reynolds
Logged In: YES
user_id=93695
What do you mean with nonlinear? If you adjust for the edges
and the middle keys are off, does this mean _both_ edges are
correct or is one edge correct and the other one is off too?
Have you tried other versions of quicktype? Maybe this is
just a bug in the current quicktype? Does this nonlinear
shift happen with other apps too?
Logged In: YES
user_id=153504
I've always had a bit of a problem getting QuickType
calibrated (any version). I struggle with having to delete
misentered characters probably 1/10 of the time. I'm
wondering if there is a smallish hardware problem in my
graffiti area.
When I describe the affect as "nonlinear" I mean that the
borders between buttons don't seem to have the same
distance between them in different areas of the keyboard. I'm
not sure how exactly to describe it. I have worked out a
happy medium in my current setup, but not every key is
as "sharp" around its edges as every other.
I've used EventAnalyzer hack in an attempt to see the
coordinates of where I'm actually tapping in the keyboard
area, but it must process the taps after QuickType, because I
don't get the X and Y coordinates that way.
I guess I'm hoping that a "debugging calibration" screen could
be added that would let users like me determine where
exactly the keys are being differentiated from one another on
the keyboard area. I.e. I tap on a key and I think it should be
in a particular key area. The form could let me know what the
actual coordinates of the tap were. That knowledge
combined with the ability to actually put X and Y values into
the keyboard map would allow me to setup the keys any way
that I wanted to in addition to allowing me to workout these
kinds of bugs.
I know this is kinda strange. I may work on a patch for it so
that you can see what I mean.
Logged In: YES
user_id=93695
With X-Master you can order EventAnalyzer before Quicktype.
This way you should get the events properly.
In another request (646247, Repeat keying), I already
suggested a separate, event manipulating hack. This way, you
could adjust the pen taps to your liking.