Peter Epstein wrote in message <5633@palm-dev-forum>...
>
>"Richard Hartman" <[EMAIL PROTECTED]> wrote in message
>news:5627@palm-dev-forum...
>> That's too bad ... I am having similar symptoms
>> (that were cleared up by checking "save behind",
>> thanks for that!).
>
>Make sure you test your app with a Palm OS 3.5 debug ROM. The debug ROM
>"fails" to save behind, because that's exactly what happens when the device
>is running out of memory. If it looks wrong on the debug ROM but works on
>the release ROM, it's an indication that you're not correctly handling the
>frmUpdateEvent. There was a discussion on this forum about exactly what to
>do when you get this event. If I recall correctly, you should make it call
>FrmDrawForm, do any other drawing that is needed, and return true (so
>nothing else tries to handle it). I think it used to be possible to just do
>any other drawing that is needed and return false, but that no longer
works.
Ok ... but I -am- doing a FrmDrawForm() and returning true ... what else?
Should I be responsible for erasing the display by calling FrmEraseForm()
for the previous form before calling FrmDrawForm() for the new one?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
