At 12:33 AM +0200 04/27/00, Ben Combee wrote:
>I'm writing my next/prevField handler for a complex form which may have some
>of its fields hidden (non-usable) depending on the other controls.
Couldn't you just store the 'form state' yourself in some other variable,
and use this as a key to figure out where to set the focus? It seems safer
to make everything depend on your own structures rather than try to co-opt
the OS's UI structures for your own purposes.
e.g. in the model/view/controller design paradigm, the Form/Field/Control
stuff is all 'view', and should be directed by the controller. So your own
'controller' code should maintain the current state and perform the 'view'
transitions (like changing the focus) as necessary. Said another way, you
don't rely on the 'view' code to save running state, that's all saved in
the 'controller' code.
--Bob
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
