From: "Evan" <[EMAIL PROTECTED]> > FrmPopupForm the new form > then FrmReturnToForm to go back previous form > -- Another alternative that sticks to standard FrmGotoForm calls is to store a property with the id of the calling form and use that to return. This isn't perfect, but avoids some issues with FrmPopForm. I honestly can't remember what they were, but I know the popup and return gave me some headaches, possibly one being that you *have* to use the return, you can't then step off to a third form. This can cause your interface to become unnecessarily constrained. Of course, if that's all you'll ever want to do then the constraint isn't an issue.
As far as the use of globals goes, I tend to implement each form in it's own module with a header to expose the interface. Properties such as returnToForm are then local to that module and managed using a setReturnToForm() function exposed via the header. While this is still global from the compilers point of view it provides good modularity for code management. Chris Tutty -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
