Re: Trellis WXEventLoop patch
"Sergey Schetinin" <[email protected]>
| Newsgroups | gmane.comp.python.peak |
|---|---|
| Message-ID | <[email protected]> |
Phillip, I see that you haven't included this small change in the trunk yet. Did you miss the request or is there a reason you don't want to add it? Thanks. On Wed, Jun 18, 2008 at 06:33, Sergey Schetinin <[email protected]> wrote: > Great. Can you still add the check to the WXEventLoop, because if > _next_time is < 0.001 then the first argument to wx.CallLater will be > zero (when converted to int by wx). > > Thanks. > >> 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! >> >> > > > > -- > Best Regards, > Sergey Schetinin > > http://s3bk.com/ -- S3 Backup > http://word-to-html.com/ -- Word to HTML Converter > -- Best Regards, Sergey Schetinin http://s3bk.com/ -- S3 Backup http://word-to-html.com/ -- Word to HTML Converter