Ichthyostega fbfbd2a078 Dispatcher+Scheduler: decision to dispose of the TimeAnchor ... several years ago, it seemed like a good idea to incorporate the link between nominal time and wall-clock time into a dedicated anchor point, which also regulates the continued frame planning. But it turned out that such a design mixes up several concepts and introduces confusion regarding the meaning of "real time" - latency can not be reasonably defined for a whole planning chunk - skipping or sliding due to missed deadlines can not reasonably handled within such an abstract entity; it must be handled rather at the level of a playback process - linking the frame grid generation directly to a planning chunk undercuts the possible abstraction of a planning pipeline		2023-05-31 03:27:13 +02:00
..
asset	Library: rectify confusingly named function on the Grid API	2022-12-05 01:05:23 +01:00
control	Functions-Commands: discard the ability to compare functors for equivalence (closes #294)	2019-06-23 19:45:30 +02:00
engine	Dispatcher+Scheduler: decision to dispose of the TimeAnchor	2023-05-31 03:27:13 +02:00
mobject	Segmentation: reorganise namespaces	2023-04-25 18:27:16 +02:00
play	Dispatcher+Scheduler: decision to dispose of the TimeAnchor	2023-05-31 03:27:13 +02:00