Tam Hanna wrote:
or why not add a decoy event for a hidden button or sth like that? Just add another button event for a button that doesn't exist, have the form handler of the second form treat it as handled so that the system doesn't see it and use it as "order" to close!
If you're going to go that route, you could probably get away with just putting an event into the queue that doesn't even correspond to a real button. Just a ctlSelectEvent with the right flags set should do it. :-) On the other hand, if you're worried about inconsistent state throwing off some of the OS code, I would put a button that's enabled and usable and all that, but just happens to be located at the coordinates (-100,-100). - Logan -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
