Thank you, but just so that you don't think I was completely at a loss, I did manage to find the command that you describe in the documentation for CodeWarrior, and thus determined the cause of the behavior. I plant to try to get control of the buttons today, so your advice is very much appreciated.
Thanks! ----- Original Message ----- From: "Logan Shaw" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[email protected]> Sent: Monday, October 10, 2005 12:00 AM Subject: Re: Databases > Del Ventruella wrote: > > Tonight I'll be looking for the: > > > > Button1_click() > > { > > > > } > > > > code for the foreseeable future. > > > > The About dialog I added in PILRIC > > > > automatically created such a button, which eliminates the form. > > > > I can't seem to find the code that actually implements the button click. > > If you open/run a form with FrmDoDialog(), then all button press events > get turned into some kind of event that causes the form to close. > Very handy if all you have is an OK button. > > If you want control of the buttons, just do FrmSetEventHandler() after > FrmInitForm() but before FrmDoDialog(). You use FrmSetEventHandler() > to cause the system to send events to your own callback function. > When your callback gets a button even (a ctlSelectEvent, actually), > if it returns false (to indicate it didn't handle the event), then > the automatic form close behavior still happens. But if it returns > true, then the automatic form close behavior doesn't happen, because > the system sees that you have handled the button press yourself. > > - Logan > > -- > For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
