Tony,
However, using the FrmHelp() API saves some program size. Second, I am more concern about displaying the help message associated with a form,
I don't think the code required for your own implementation of a FrmHelp would cause all that much bloat. And you can still draw the i icon in the title bar and handle events for it yourself too, so the interface remains the same to the user.
So I still wish the next Palm OS can improve their FrmHelp() API.
Whether or not they change FrmHelp() in the future, that doesn't alleviate the problem now on current devices. And even if a future glue library provided an alternative, that adds code to your program just as your own solution would, so there isn't much reason to not roll your own if you are dissatisfied with the current implementation.
JMHO, Doug
Thanks for sharing.
In general, I understand it's always possible to use custom routines, whenever one is dissatisifed with the OS's interfaces. There are pros and cons to every approach.
It's a question whether you want consistent behavior across all OS versions, or you want your application to appear consistent to all other applications in a single Palm OS device. In the first case, you would use your own customized routines. In the latter case, it may be better off to let the OS handle it.
You are right.
Tony
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
