> I now see the picture. > > As I wrote in the previous email, it seems that we currently are not blocked > waiting for vsync(), at least on Windows with D3D pipeline. Anyway, even if > we "fix" that, what you propose is that sometimes both threads will be > blocked (the render thread waiting for vsync, the event thread waiting for > the render thread), which doesn't sound perfect.
Right. That stinks. > Note that on Windows and Mac OS X, input events and application runnables are > handled differently at the native level (either using different mechanisms, > or having different priorities). To implement this proposal, we'll need to > eliminate the difference, which may be a difficult task. Are the application runnables at a higher or lower priority than input events?
