Jim McGowen wrote:
The Tungsten C produces 2 key down events for each button press. NavKeyPressed doesn't work for the 1st event but does for the second one. Same with NavSelectPressed. Almost the same thing with the T5 except I only get 2 key down events with the select button. The extra event will cause problems in some of my handlers beacause they need to handle other non-5-way key down events. I'll write an ugly special case for them if I have to.
Isn't that what Ben was getting at when he mentioned how some devices send another keypress if they you don't indicate that you've handled the first one? He was mentioning the center button on the the T5 and Treo 650, but it might apply to other buttons as well. Have you tried returning true from your event handler whenever you handle those events? From the code you posted, it looks like you aren't returning true anywhere where you handle stuff, and I wonder if that could be part of the reason you're getting two keystroke events for one physical keystroke. - Logan -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
