Capturing a window that is completely covered
Perch lets you keep working while a window is shared, but that only works if a buried window keeps producing frames.
Capture keeps up
On Windows, the Desktop Window Manager keeps an offscreen surface for each window, and Windows.Graphics.Capture reads that surface rather than the screen, so a window buried behind a full-screen editor still captures.
Chrome doesn't
Chrome, on the other hand, computes window occlusion on Windows and stops rendering a window that's fully covered. The capture stays healthy and delivers the same still frame forever, which looks exactly like a capture bug. Since Perch launches its own Chrome, it adds two switches:
--disable-backgrounding-occluded-windows --disable-features=CalculateNativeWinOcclusion
macOS needs neither, because Chrome there was measured not to throttle covered windows.
A limit stated plainly
A minimised window has no compositor surface, so it can't be captured, and the interface says so instead of showing a frozen frame. In measurements, a covered window gave 102 frames, 60 of them distinct, with scrolling still forwarded, a minimised one gave zero frames, and a restored one gave 83.
This is a shorter version of a post on the Pioneering blog, so if you want the full story, read the original on pioneering.app.
Next postPerch 0.18: one file, per-user, no admin
