Code review comment for lp:~vanvugt/mir/physical-frame
Revision history for this message
| Chris Halse Rogers (raof) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
So, the first point - provide on client request only - can be more easily handled further up the stack.
The second point - that there might be some future Display that can't provide vsync events information but *can* tell you frame timing - is already going to have a bad time in Mir. If we can't detect frames our compositor is going to spin at 100%, and if we provide a synthetic vsync then... we've got vsync events ☺.