At 15:16 2002-10-7 -0700, you wrote: >At 5:08 PM -0500 10/7/02, Ben Combee wrote: > >At 18:06 2002-10-7 -0400, you wrote: > >>I'll be able to provide a stack trace tomorrow (home from work for the > >>day), but one place I saw it was within the SysGetEvent API, where at some > >>point it calls a function to validate the form (or window) pointer. I'm > >>calling FldNewField from my frmOpenEvent handler, so perhaps there are > >>events that are in the queue containing the old form pointer? > >> > >>If the calls being in the frmOpenEvent handler are the cause, then is > >>there a better way to do this or do I just live with it? > > > >Are you using FldInsert or the ilk to modify fields after you add them > with FrmNewField()... if so, that would fire a fldChangedEvent which > would have an embedded pointer. > >Yes, but wouldn't that embed the new, current, updated pointer? If so, >then that shouldn't be the problem. He'd have a problem if he did any of >that *before* he added the new field.
If you add field, modify, add field, modify, and so on, you'd have flcChangedEvents with potentially bad pointers, since inserting the later field pointer could invalidate the previous ones. -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead Palm OS programming help @ www.palmoswerks.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
