Christopher Faylor writes:
 > An NT only solution is not a solution.

I wasn't for a moment suggesting that it was.

 > Syncing every "x" seconds also is not a solution.
 > 
 > The correct solution is to resync after events which cause the clock to
 > stop.

OK, I'll have a crack at this over the weekend following David's
hints.

Looks straightforward. I'll patch the event loop in window.cc to set
some static flag in hires on suspend and/or resume events, and
reinitialise in hires::usecs iff the flag is set.

Let me know if I'm well off track here.

- Phil


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to