At 1:37 PM -0700 1999/04/12, David Mottern wrote:
>>During a call to "FrmAlert" I'm receiving the following message:
>>
>>"ScrDriverNew.c, Line:499, Invalid Params"

Line 499 is the error exit handler within the routine ScrCopyRectangle. A quick scan of the source tells me it could be...

-- the copy mode is something other than scrCopy

-- the srcWinP->gDeviceP->compressed flag is set and the fromX or fromY parameters are non-zero

-- the blitter notices that srcRowBytes > scrMaxLineBytes (40 bytes) which seems to be another way of saying the (probably compressed) source bitmap is too big

I'm sure there are more possibilities, but I thought I'd throw these out as a starting point. Can you drop into the debugger when the error occurs? What's the stack trace look like? I'd be interested to know if the error occurs right away at the start of FrmAlert, during a redraw operation, or when the form is dismissed.

Regards,

Jim Schram
3Com/Palm Computing
Partner Engineering

Reply via email to