At 7:52 PM +0100 12/05/99, Mike Musick wrote:
>This was fine through OS 3.3. With 3.5, it'll crash whether the current
>form is init'ed, rendered, or otherwise - which supposedly shouldn't matter
>anyway. Do we now have to explicitly declare a window first? Any other
>thoughts?
You say that this crashes even if the form is rendered already? That's
very disturbing -- I'd really like to track this down.
We did change the behavior in OS 3.5 so that the current global draw window
would be invalid (a bad pointer) rather than simply NULL. We did this to
help track down apps that used to trash low memory. It sounds like that
change is catching your app.
But, as long as the draw window is valid, then the call won't crash.
So, are you sure it really crashes after FrmDrawForm has been called for
your form??
--Bob
