Gah! Is there any way of turning off this extra "functionality".
Using debug I've mapped the newer keycodes, so my app works similar to how
it used to, but the object navigation model is fighting my software.
I'm using codewarrior 9.3, but I'm seeing events that are undocumented or
(or at least aren't in the include files I'm using).
For example what's 0x4000,0x4003, or 0x0000
I would consider using the glue library (even though it adds a large
overhead to my code) but I'm worried that the glue library might be out of
date, since my header files seem to be. Using CodeWarriour 9.3 Is there an
update I should be using?
Chris Bruner
Compulife Software Inc.
==============================================
----- Original Message -----
From: "Ben Combee" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[email protected]>
Sent: Wednesday, March 22, 2006 5:27 PM
Subject: Re: Fw: Tungsten E vs Tungsten E2 (5 way button problem)
On 3/22/06, Chris Bruner Compulife <[EMAIL PROTECTED]> wrote:
I've got the 5 way button working beautifully on the Tungsten E but my
customers are saying it's not working on the E2 or the Trio's..
What is different? Can anyone point me to sources for using both the E2
and
the E's 5 way?
The newer palmOne and Palm devices uses a different set of keycodes
for the five-way navigator and also support an object navigation
model. There's a KB article at palmsource.com on the different
schemes, and you should also read the Palm Developer Guide from
pluggedin.palm.com.
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
