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


Previous by date: 23 Dec 1999 17:35:33 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next by date: 23 Dec 1999 17:35:33 -0000 Re: blitting with more than 8bpp, Greg Haerr
Previous in thread: 23 Dec 1999 17:35:33 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next in thread: 23 Dec 1999 17:35:33 -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: 23 Dec 1999 17:35:33 -0000
Message-Id: <008501bf4d5a$9ab1c440$15320cd0@gregh>

: One solution that worked for me was to change the signatures
: of GsCheckMouseEvent & GsCheckKeyboardEvent to return a
: boolean indicating whether or not an event was posted. I use
: this information to keep "pumping" mouse events as long as
: there is one.

Well, it's probably OK to have the signatures tell us something
we can't know now, but a better solution would be to increase
the size of the serial interrupt or clist buffers.

Also, there are subtle issues involved with pumping events
without returning from GsSelect.  But also you might just
loop while rtems_event_receive says there's events.

I still prefer the increased serial input buffer size, to be safe.

Greg


Previous by date: 23 Dec 1999 17:35:33 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next by date: 23 Dec 1999 17:35:33 -0000 Re: blitting with more than 8bpp, Greg Haerr
Previous in thread: 23 Dec 1999 17:35:33 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva
Next in thread: 23 Dec 1999 17:35:33 -0000 Re: Help --- assert( drivers/mempl4.c, line=237 ) --- follow up, Rosimildo daSilva


Powered by ezmlm-browse 0.20.