Code review comment for lp:~vanvugt/mir/unocclude
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hey I don't mind occlusion logic staying, but it is contradictory to non-blocking efforts. Choose one or the other.
I built the occlusion detection logic to block occluded clients. Its purpose is to block occluded clients from rendering, per bug 1227739. And it does that well.
If you choose both to have occlusion detection and non-blocking then you also require extra work (in pending proposals) to make them play together. Because the occlusion detection is only doing its job in blocking client rendering.