Just tried it again on the device and it worked! Before, I tried it on the
Garnet simulator(PalmSim_54_dbg.exe) when I got the 0x505. Didn't know
there was a T5 specific simulator, I'll have to go find it.
Ok, cool, but it still works the same on the T5. I still get 2 key down
events for the select button regardless of returning true or false and the
seconds one is the one that gets processed... and I still have to use
if( NavDirectionPressed( event, Up ) || event->data.keyDown.chr ==
vchrPageUp )
So what does FrmSetNavState( fp, kFrmNavStateFlagsInteractionMode ); do for
me again?
My setup is: CW9.3, Palm_OS_68K_SDK_Fall_2004_CW,
palmOne_SDK_5_0_palmOneHeadersPublic, pilrc3.1.
System access path to {Compiler}CW for Palm OS Support\(Other
SDKs)\palmOneSDK
and I'm using POL.
p.s. Thanks everyone for the responses... much appreciated.
"Ben Combee" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> At 06:40 PM 9/1/2005, you wrote:
>>Tried FrmNavSetState() on the T5, got 0x505. FrmSetNavSate() is defined
>>in
>>HsNav.h. Thought that's what they meant by "HsNav" functions.
>
> Which version of the palmOne SDK are you using? What about the Palm OS
> 68K API SDK? I just built a test app using CW 9.3 that calls both
> FrmGetNavState and FrmSetNavState and it ran without error on my T5
> Simulator. I don't have an actual device here in Austin to check this on.
> This was using palmOne SDK 5.0 and the PalmSource 68K API SDK from Fall
> 2004.
>
> I wonder if you're getting an HsNav.h file from an old source? When I
> cross reference it, I'm getting the definition from the PalmSource header
> Form.h...
>
> Err FrmGetNavState (const FormType* formP, FrmNavStateFlagsType*
> stateFlagsP)
> FRM_NAV_TRAP(NavSelectorFrmGetNavState);
>
> with the selector number defined in the same file as
>
> #define NavSelectorFrmGetNavState 0x5
>
> and the FRM_NAV_TRAP defined as
>
> #define FRM_NAV_TRAP(frmNavSelectorNum) \
> _SYSTEM_API(_CALL_WITH_UNPOPPED_16BIT_SELECTOR)( \
> _SYSTEM_TABLE, sysTrapNavSelector, frmNavSelectorNum)
>
> For includes, I just have these three lines at the top of my file\
>
> #include <PalmOS.h>
> #include <PalmOSGlue.h>
> #include <palmOne_68K.h>
>
> with a system access path pointing to my palmOneSDK/Incs folder.
>
>
> -- 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/
