From: "druid" <[EMAIL PROTECTED]> > I have to many fields for one form > So I want to make a popup form for some of the checkbox fields > I was going to use a FrmPopupForm call then a FrmReturnToForm(0) > call to go back to the origional form. > This can cause problems if it's not done carefully. You should review the archives of this forum for more info.
> I guess I could make global variables, but is their a better way > to do this. > If you mean having a global structure that stores data shared by fields spread across several forms then I think this has the solid advantage of making it much easier to move fields between forms or add other forms as you extend the project. This is true regardless of whether you use a popup or not - you want to avoid having the data management for the app hard-coded to the fields that happen to be on each form. If your app is getting to this size it's time (past time?) to create a code module to manage the data separately from the form code. This module would have the code to load and save the data from the database and would either expose globally visible variables or, more work but better, expose get~ and set~ methods for each property. Just because you're coding in C doesn't mean that you can't use the object-oriented concepts of data hiding and interfaces. They're really just old C concept anyway. I guess it's obvious advice, but a great deal of the simple examples for Palm have the field management logic in the same functions that implement the forms so it's easy to extend these simple examples without stopping to think that at some point their underlying design has to be re-examined. Chris Tutty -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
