Yepp, I had the same problems. I had thought of a very smart solution
working with dynamic controls but someone told me my app has to run on 3.5
so I had to introduce a very stupid way of dealing with static controls to
achieve the same thing :(..

/Henrik

"Chris Antos" <[EMAIL PROTECTED]> skrev i meddelandet
news:109359@palm-dev-forum...
>
> What OS version?
> Older OS versions have bugs in the dynamic form/control APIs.
>
> * OS 4.1 is the first OS version where they work correctly.
> * OS 4.0 is almost right, except that for List objects it only updates the
> pointer for the _first_ item in the List.  You can fix up the other
pointers
> manually, with a little bit of code.
> * OS 3.5 and lower and just broken.  They look for sequences of bytes that
> "look" like pointers, but frequently it's really just the last three
> characters in a string, or other false positives that cause more than just
> "cosmetic" corruption.
>
>
> "David McNab" <[EMAIL PROTECTED]> wrote in message
> news:109353@palm-dev-forum...
> >
> > Hi,
> >
> > I'm starting to get into dynamic forms.
> >
> > After I've created a form dynamically, FrmGotoFrm() displays it
> > perfectly.
> >
> > But the second and subsequent times I call FrmGotoFrm() for that form,
> > the title is showing up corrupted. So far, there's not much on the form,
> > but I anticipate that corruption of form objects might happen as well.
> >
> > When I get the FrmLoadEvent, I'm just setting an event handler and
> > setting the form active.
> >
> > When the form's event handler gets the open event, it calls FrmDrawForm
> > and indicates the event is handled.
> >
> > When the form's EH gets frmCloseEvent, it does nothing, but indicates
> > the event has been handled.
> >
> > The form's title is set from a string whose space (including null
> > terminator) has been allocated via MemPtrNew(). I've no idea why this
> > string is getting over-written.
> >
> > I need to ask - is it reasonable to indicate that the frmCloseEvent has
> > been handled, even though my handler is doing nothing? (Because if I
> > don't indicated handled, the form is getting destroyed by PalmOS).
> >
> > Or is it 'better behaviour' to allow PalmOS to destroy the form on
> > frmCloseEvent, and should I instead re-create the form before I
> > re-display it?
> >
> > And is there any reason why the form's title is getting scribbled over?
> >
> > By the way - if I re-create the form with FrmNewForm(), it displays
> > perfectly.
> >
> > Thanks for any advice
> > Cheers
> > David
> >
> >
> >
> >
>
>
>
>



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to