> By the way, > how do the time selection dialog and the font dialog > handle things like this?
The time selection dialog uses stack-based variables to hold the current result. Instead of setting up an event handler, it just includes the entire event loop in-line. This lets it access these stack-based globals. I don't think I'd recommend this solution! :) The font dialog takes advantage of the fact that FrmDoDialog doesn't delete the form. It calls FrmGetControlGroupSelection after FrmDoDialog returns. Once it's got the result, it calls FrmDeleteForm to clean up. Before it calls FrmDoDialog, it calls FrmInitForm and then sets the initial state with FrmSetControlGroupSelection. This technique works well when the form objects hold all the state you need. Features are fine too. - Danny -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
