I have noticed two issues in regards to fnav which I would like some input on - confirmation, explanation, whatever anyone can offer. I should point out that these examples are from test apps written with NSBasic using an fnavxxxx.bin resource file which was created with PilRc. The tests were run on a Treo 700p.
1) Certain form objects do not appear to be navigable, even when they are specifically included in an fnav resource file navigation map. A map which goes from: button button field gadget field label button will navigate a focus ring like this: button button field [nothing] field [nothing] button In other words, gadgets and labels do not appear to be navigable. 2) In test apps, if I tap into a field, change it's contents, and then tap out of it, the field's code block runs as expected. However, if I use the 5-way to *navigate* into the same field, change it's contents, and then navigate out of the field, the field's code block *does not* run. In fact, the result is the same if I tap into the field and then navigate out, or navigate into the field and then tap out. The code runs *only* if I both tap in and tap out of the field. Is this expected behaviour? -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
