[Qt-interest] QTimer on Windows in Unreliable for Small (16ms - 30ms) Delays

[Josiah Bryan]

Jeffrey Brendecke wrote:
> -----------
> On Saturday 05 September 2009 05:50:12 you wrote:
> 
>>> * In the main thread, on each time out, pull a rendered frame from the
>>> queue and display it. If the ticks are not getting swallowed due to
>>> whatever external constraints, then it seems the rendering would need to
>>> give, stopping rendering and going on to the next frame if it did not
>>> finish in time. Maybe some sort of interlacing could result in at least
>>> the frame getting covered from top to bottom, though not on every line.
>> Sounds interesting - not sure how to implement that - care to elaborate
>> any more?
> 
> Interlacing here means, e.g., draw odd rows first, then fill with the even. 
> Whether this would help or not would need to be investigated and determined 
> based upon where the real bottlenecks are.

Gotcha - understood the interlacing part, just want sure how the thing 
was envisioned to fit together - e.g. the stopping rendering and going 
to the next frame in time. I dont think the "drawImage()" function in 
QPainter is interruptable - and that should happen quite fast anyway. I 
might be just too deep in details, and its probably quite clear to 
everyone else anyway. :-) But, thats for the info though.

I'm out for the evening (almost 1am here) - back at it tomorrow 
sometime. Cheers!