Re: Trellis WXEventLoop patch

At 11:11 PM 6/17/2008 -0400, Phillip J. Eby wrote:
>At 04:29 AM 6/18/2008 +0300, Sergey Schetinin wrote:
>>If that sounds like a bug, I think I know
>>what minimal wx app will reproduce the problem.
>
>If you can manage it without wx, that would be even better.  I think 
>I see the way you could end up with a negative value, but I'm not 
>clear as yet how I could *force* that to occur.

Never mind - I figured out how to force it to occur in a test, and 
have fixed the bug.  next_event_time() is now tested to not return 
zero or negative numbers when time advances, and the underlying 
problem (not depending on the rule that removed the already-occurring 
events from the schedule) has been fixed in SVN.  Thanks for the bug report!