Is it really bad to have FrmValidatePtr() in release code? It says so in the SDK reference. But why?
I have a popup dialog form (EditNameDialogForm) which I use FrmPopupForm(EditNameDialogForm) in my main form to call. Now, EditNameDialogForm can also be called from AddDelNameDialogForm, which in turn is called using FrmPopupForm(AddDelNameDialogForm) from my main form. My question is, how can I programmatically find out whether the main form or AddDelNameDialogForm is the predecessor of EditNameDialogForm? I thought of using a global stack to store the pointers of active forms, but I'ld rather not. I'm using FrmValidatePtr() to test which forms are active. So, the reference says it is bad to have FrmValidatePtr() in release code, why? Now, in the User Interface document of the KB (http://oasis.palm.com/dev/kb/manuals/1788.cfm), it says to use it, to make code more robust. So, now, can someone tell me why it is bad to have FrmValidatePtr(). Is there a real issue here or is it just a philosophically no-no? -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
