One named stream a SpatialCapture (or save_spatial_snapshot) writes into a SpatialCache each tick. More...
#include <SpatialTransfer.hpp>
Collaboration diagram for MayaFlux::IO::SpatialCaptureSource:Public Attributes | |
| std::function< bool(SpatialCache &, const std::string &)> | capture_frame |
| std::string | stream_name |
Detailed Description
One named stream a SpatialCapture (or save_spatial_snapshot) writes into a SpatialCache each tick.
capture_frame receives the cache and this source's own stream_name, so one SpatialCapture can drive several distinct sets into one archive on one clock: several operators on a network, a network stream alongside a grid stream, and so on. A caller wanting independent cadences, or several independent writers landing in the same archive as their own updates arrive, instead constructs several SpatialCapture instances (or writes directly through SpatialCache::write()) against the same shared_ptr<SpatialCache> IOManager::capture_spatial() hands back for a given filepath; nothing here assumes it is the only writer touching that cache.
Definition at line 32 of file SpatialTransfer.hpp.
The documentation for this struct was generated from the following file:
