Ben Combee wrote: > > At 08:56 PM 8/31/2005, you wrote: > >NavDirectionPressed works great for the TC but NavDirectionPressed( event, > >Up ) and NavDirectionPressed( event, Down ) don't work for the T5. > > > >This DOES work on both: > >if( NavDirectionPressed( event, Up ) || event->data.keyUp.chr == > >vchrPageUp ) > >if( NavDirectionPressed( event, Down ) || event->data.keyUp.chr == > >vchrPageDown ) > > Read the comments in the header file -- you need to set your form into > object interaction mode or up/down will just send pageUp/pageDown > keys. This is also described in the palmOne development guide. >
Ben, I've also been struggling with the 5-way navigator. I'm hoping that the NavDirectionPressed and the IsFiveWayNavEvent macros will work for both the Zire 31 and the TE2 (I'll test on hardware this afternoon). I think a good portion of my struggling has been due to all the 5-way navigator variations in the documentation and sample code. As an example, the palmOne Development Guide describes "interaction mode". Your comment above is about "object interaction mode". The palmOneNavigator.h header file suggests setting the focus state to "object mode". Are "interaction mode", object "interaction mode", and "object mode" all the same thing? And what API should I use to accomplish setting a form to object interaction mode? (I have a form with a table and I'd like to use the 5-way navigator as an aid to traversing the rather lengthy table rather than as an aid to setting the focus.) - Greg -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
