Skip to main content

Module capture

Module capture 

Source
Expand description

Screenshot checkpoints. A revision identifies one ordered request, not a timer or an image hash. Completion of an older request cannot release a newer checkpoint.

Structs§

Fence
UI-thread-owned state for an asynchronous capture checkpoint. Clones share state. Keep one per native window. Callbacks may outlive a timed-out request: complete deliberately ignores them after another revision has started.

Enums§

Readiness
How a toolkit establishes freshness for a screenshot.

Functions§

holds_settled
Whether every registered hold has settled. Holds run outside the registry’s lock, so a hold may register another.
register_hold
Register a capture hold for the life of the process. Register once per host: every registration is consulted on every capture.

Type Aliases§

Hold
Whether a host that presents frames of its own has every frame it owes on screen.
Day API ↩ Guides· daybrite.dev