I should have added some more details about this. It occurs during a call
to FrmAlert. My alert has 3 buttons. If I tap any of them I get the error:
"ScrDriverNew.c, Line:499, Invalid Params"
This happens within FrmAlert, It never returns from the call. But it does
remove the alert box before failing. This started occurring after I
installed the latest CW patch. It didn't occur before and I don't think
I've changed anything. It's just a plain vanilla confirmation alert created
with Metroworks Constructor.
-----Original Message-----
From: Bob Ebert [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, April 13, 1999 2:09 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Debugger Error Message
At 1:37 PM -0700 4/12/99, David Mottern wrote:
>"ScrDriverNew.c, Line:499, Invalid Params"
>
>Does anyone know what might be causing this?
It's in the code that draws bitmaps. Beyond that, it could be any of
several things, and only stepping through the code will really tell you.
The most likely cause is that it's trying to draw a compressed bitmap with
invalid data, or drawing a bitmap with incorrect copression flags.
If your alert has form bitmaps in it, you might check to see if they're
being correctly generated. Otherwise, it could be coming from the 'saved
bits' bitmap that is being restored when the alert closes. Exactly when
during FrmAlert does this occur? If it's when the alert opens, it's
probably a bitmap in the form, and if it's when the alert is dismissed,
it's probably the saved bitmap.
--Bob
