Daniel McCarty wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > I doubt you'll get the information you need to TP3Data and TP3DictState
> > (though I could be wrong). Could you describe what you're really trying to
> > do? Perhaps there's another way of accomplishing that task?
>
> (I can understand if Graffiti(R) technology <g> is something still
> covered by Palm as a trade secret and they have no desire to release
> the source. So if releasing this information isn't doable, I'll just
> go back to doing this my old way.)
> I'm assuming that the lastChar member of the GrfGlobalsPtr contains
> the last character entered. This would solve me having to save the
> Char on my own and allow me to pack more information into a feature.
> I can't resolve the offset for lastChar without knowing something
> about TP3Data and TP3DictState, though. I wouldn't mind just knowing
> their sizes so I could create a dummy struct to make the compiler
> happy.
>
> Thanks,
> Daniel.
>
> >
> > Daniel McCarty <[EMAIL PROTECTED]> had written:
> >
> > I've been trying to use GrfGlobalsPtr but I've come up against a
> > problem because the headers distribution apparently doesn't include
> > (no pun intended) P3API.h and whichever other headers contain the
> > definition for the TP3Data and TP3DictState types.
> > Does anyone know how I could get this information? Is it covered
> > under a separate NDA other than the one for the sources?
> > (Disclaimer: I'm only trying to read one byte from the global,
> > no writes are involved and I promise to be nice and check which
> > version of the OS I'm operating on.)
> > Thanks,
> > Daniel.
Actually, Dan is not the only person to want and need the Graffiti(TM)
internal state information. We have a "keyboard" (well, an input method
- not T9) that would be qualitatively better integrated with the device
if it were to have both read and write access to Graffiti's states. So
far, on purpose, I have avoided diddling with the various bits and such.
But no one likes to make the choice of either:
A) Diddling with OS bits.
or
B) Integrating with the device in a looser manner than what should be
the case.
So this is a vote to expose the Graffiti states through the API.
Thanks,
Alex Robinson
[EMAIL PROTECTED]
-eom-
