nanogui: Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up


Previous by date: 22 Dec 1999 03:26:24 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next by date: 22 Dec 1999 03:26:24 -0000 blitting with more than 8bpp, Kyle Harris
Previous in thread: 22 Dec 1999 03:26:24 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next in thread: 22 Dec 1999 03:26:24 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva

Subject: Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up
From: "Greg Haerr" ####@####.####
Date: 22 Dec 1999 03:26:24 -0000
Message-Id: <000801bf4c1a$cf10ab20$15320cd0@gregh>

: Left button == 0x04
: Right button == 0x01
: Both buttons == 0x05
: 
: So, it looks good when running the test driver.
: 

Perhaps it's your GsSelect code that calls GsCheckMouse
and GsCheckKbd even when timeout returned.  And
then the mouse driver is called twice, and returns
data twice?

If that's not it, go into the GsCheckMouse code and 
trace through the code leading up to the WM_LBUTTONDOWN
that is being created.  It's values should be the same as
any previous or post WM_MOUSEMOVE messages,
since they are generated in addition to the GdMoveCursor,
which actually moves the cursor on the screen.

Finally, you might want to make sure that the same code you're
running runs OK on a normal Linux box, just in case.

Regards,

Greg



Previous by date: 22 Dec 1999 03:26:24 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next by date: 22 Dec 1999 03:26:24 -0000 blitting with more than 8bpp, Kyle Harris
Previous in thread: 22 Dec 1999 03:26:24 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next in thread: 22 Dec 1999 03:26:24 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva


Powered by ezmlm-browse 0.20.