At 10:26 AM 9/1/2005, you wrote:
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.)
There are two implementations here... the old palmOne navigations keys and
the newer PalmSource nav keys combined with object interaction. For an
overview, please see the article I wrote when I was at PalmSource at
http://kb.palmsource.com/cgi-bin/palmsource.cfg/php/enduser/std_adp.php?p_faqid=909
The best way to get a form into object interaction mode is to provide a
'fnav' resource for the form that describes the navigation order. This is
done in PilRC using the NAVIGATION keyword; there's an XML form for this in
PalmRC used by PODS, and there are templates published for Rez if you're
using Constructor-format resources.
-- Ben Combee, Senior Software Engineer, Palm, Inc.
"Combee on Palm OS" weblog: http://palmos.combee.net/
Developer Forum Archives: http://news.palmos.com/read/all_forums/
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
