> Support for 'fnav' resources is built into PilRC 3.0 and later (my > favorite way to specify them) and also is in the current PalmRC > compiler in the PODS environment, although you need to write all > the XML yourself.
I use PODS. Writing the XML stuff was just a minor annoyance; not really a problem - once I understood what the various elements meant. >See also http://palmos.combee.net/blog/TungstenT5NavigationAPICh.html I couldn't access that URL; I'll try again later. > The most recent Palm OS 68K API SDK (the Fall 2004 release) has > an updated glue library with FrmNavGlue functions for handling > the Treo 600 and later devices correctly. Ah! Thanks for turning my attention to this. I had started using the Treo-specific headers and was having a hell of a problem. You see, since I want to support Tungsten E too (this is, after all, the device that I have), I do some poor man's 5-way navigation - only through the buttons of the forms, not through the other form elements and not through the buttons of the dialogs. Since I have to do it manually (by listening to the keyDown event and emulating the ring by turning the button's frame to bold), I had installed the 4.1 SDK, in order to use the nav* macros to check the 5-way control of the Tungsten E. Then I added the Treo-specific headers, trying to use stuff like HsNavObjectTakeFocus and hsFtrIDNavigationSupported and was having conflicts, because the HsNav.h file in the SDK 4.1 was found before the file with the same name in the Treo-specific include files, yet it didn't contain the definitions I needed. But, after reading your message, I switched to using the glue functions only (FrmGlueNavIsSupported, FrmGlueNavObjectTakeFocus) and I no longer need the Treo-specific include files, so everything works fine. Can I use the glue API to handle the Tungsten E 5-way navigator too? I don't think so, but just asking. Another thing - I really dislike this "we don't support cycling" that is all over the documentation of the Treo 5-way navigation. Why not?! It's so natural and convenient that when you're on the leftmost element and press Left, you should go to the rightmost element. Is there an *easy* way to implement cycling myself? Implementing cycling in vertical direction *is* easy - I just specify in the fnav resource that the "above" object of the topmost object is the bottomost object and the "below" object of the bottommost object is the topmost object. But what about cycling horizontally? If the 5-way navigation is supported, I don't even listen to the keyDown events - so I can't detect that the user is pressing Left when on the leftmost object or Right when on the rightmost object... Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
