If you'll look at the original message here, it seems that somehow a message of mine from early December was reposted. FYI, I have since figured everything out and have my app working quite well with the one-handed navigation feature, and this includes some pretty complicated forms (graphic buttons, scrolling tables, controls optionally enabled/disabled, etc.). I did learn a lot about this feature in general and how to work around some of its deficiencies.
-- My graphic buttons are rectangular, but the system default is to draw a focus ring with rounded corners on a button, so I have to handle this myself to draw the rectangular ring (strictly a cosmetic issue, but it does look a lot better). -- After displaying a dialog, menu, etc. it seems to be a bit inconsistent as to whether the previous focus state and ring are correct when returning to the original form. I generally had to refocus on the object to make sure it was correct. -- When doing things like scrolling a table, it's necessary to remove the focus ring if it's drawn around a table cell *before* redrawing the table. Otherwise, the "save-behind" data for the ring of course will not match the new table contents. -- Making an fnav resource for every form is the only way to make sure that everything works correctly, especially if you have non-default-behavior controls (e.g., tables) or controls that are optionally hidden. In some places, handling all this made a bit of a mess of my code, which of course was designed a couple of years ago without any consideration for this feature. But we all know how that goes... Doug G http://www.gedstarpro.com -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
