4 ms·
I think you're right. It used to be practice to limit your invalidation rect/region based on known bound information. Now every developer treats their entire bu
by andrewmcwatters 3y ago
I think you're right. It used to be practice to limit your invalidation rect/region based on known bound information. Now every developer treats their entire buffer as a cheap throwaway and they couldn't be further from the truth.
- mike_hearn 3y agoIt's still done. JavaFX does dirty region tracking for example, e.g. here https://github.com/openjdk/jfx/blob/master/modules/javafx.graphics/src/main/java/com/sun/prism/es2/ES2SwapChain.java#L55 https://github.com/openjdk/jfx/blob/master/modules/javafx.gr... and that's a toolkit that's still relatively modern (it was ahead of its time). For example the UI thread is separated from the rendering thread, so one core can be computing the layout/processing events/doing animations for one frame whilst another core renders another frame to a GL/D3D command stream.