lumiera_/tests/core/steam/fixture
Ichthyostega a1c1456849 Job-Planning: dispose of FrameCoord in pipeline and Dispatcher interface
...as a preparation for solving a logical problem with the Planning-Pipeline;
it can not quite work as intended just by passing down the pair of
current ticket and dependent ticket, since we have to calculate a chained
calculation of job deadlines, leading up to the root ticket for a frame.

My solution idea is to create the JobPlanning earlier in the pipeline,
already *before* the expansion of prerequisites, and rather to integrate
the representation of the dependency relation direcly into JobPlanning
2023-06-18 03:50:48 +02:00
..
fixture-change-detector-test.cpp Dispatcher-Pipeline: prepare test for the new NodeGraphAttachment 2023-06-07 04:03:00 +02:00
fixture-segment-test.cpp Job-Planning: dispose of FrameCoord in pipeline and Dispatcher interface 2023-06-18 03:50:48 +02:00
model-port-registry-test.cpp Dispatcher-Pipeline: prepare test for the new NodeGraphAttachment 2023-06-07 04:03:00 +02:00
node-graph-attachment-test.cpp Job-Planning: frame number now additionally required in FrameCoord 2023-06-17 03:10:57 +02:00
segmentation-integration-test.cpp Dispatcher-Pipeline: remould Segment for on-demand JobTicket generation 2023-06-08 03:21:43 +02:00