Re: Assertion failure int event-msw.c
>>>> Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes:
Andy Piper wrote:
>
> >> At 08:52 PM 3/10/99 -0500, David Bush wrote:
> >> >On repeated exposure events in the Cygwin build I get an assertion
> >> >failure in mswindows_dequeue_dispatch_event. I've never looked at
> >> >this code before so there is little chance I could resolve the issue
> >> >by the deadline for the next beta.
Jonathan> [snip]
>
> Jonathan you know the event code better than me - to me the
> assertion seems a little OTT, could we maybe make the failure
> slightly less brittle and discard events that we don't think
> should be there?
Jonathan> My knowledge is a little rusty, but I'm pretty sure that
Jonathan> the assert is good. Just from looking at the code this
Jonathan> looks potentially suspect in mswindows_need_event():
There also seems to be a mismatch between the call to
mswindows_dequeue_dispatch_event in emacs_mswindows_next_event
and the actual function. IT is being called with the argument
!NILP(mswindows_u_dispatch_event_queue) but does not have any
arguments. This suggests that there was a change of direction that
wasn't fully realized. I spend some time in the CVS history searching
for enlightenment.
david