My app has a form where I load and draw a bitmap in its draw routine.
When Gremlins is simulating low-memory conditions, frmUpdateEvent is
sent after a system dialog (like Find) obscures the window. When I
call the draw routine, Gremlins complains about invalid parameters to
ScrDriver/ScrDriverNew.
When I step through this event, the bitmap resource is loaded and the
structure appears correct prior to the WinDrawBitmap() call. After
the crash, the height of the bitmap has been magically changed to 160,
apparently inside WinDrawBitmap(). Of course, this code works
perfectly when the form is drawn initially. Argh. Has anyone seen
this sort of thing before?
--
-M- [EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
