At 05:36 PM 9/1/2005, you wrote:
at least i'm close :)
I went through the reference but can't find the glue equivalent to
FrmSetNavState().
Oops... I thought I'd wrapped all of the FrmNav functions, but in fact, the
FrmNav functions that are in the glue library are the ones that have
different trap values on the Treo 600 and the later devices. The ones with
the same trap numbers aren't defined with glue; you just guard calls to
them with a call to FrmGlueNavIsSupported to see if they can be called.
The T5 should be able to handle FrmSetNavState... it's only the earlier
devices (T3, E, etc) that don't have the FrmNav APIs at all where you get a
0x505 error.
The warning you saw in the dev guide was about "HsNav" functions -- some of
those were renamed to FrmNav with the same trap numbers and are OK on all
devices with navigation, others were moved to different trap numbers --
those are the ones that have glue, as I mentioned above.
-- 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/
