This is a first draft as of 1/2009, and likely to be superseded by a better design, where rather the provider of an output facility registers with the OutputManager in the core.
This is a first draft as of 1/2009, and likely to be superseded by a better design, where rather the provider of an output facility registers with the OutputManager in the core.
This is a first draft as of 1/2009, and likely to be superseded by a better design, where rather the provider of an output facility registers with the OutputManager in the core.
12/23 this feature seemed necessary in the first implementation, yet after integration and follow-up refactorings (NOTIFY-handling) it turned out both superfluous and potentially dangerous, since it creates additional management work and possible contention on the Grooming-Token. The way NOTIFY-activities are handled now already ensures that they are activated only after their target's start time.
this is defunct code, left over from the old GTK-2 GUI of Lumiera. Deactivated since 2016 and no longer included since 3/23 but left in tree for later reference
this is defunct code, left over from the old GTK-2 GUI of Lumiera. Deactivated since 2016 and no longer included since 3/23 but left in tree for later reference
when we switch our primary type sequence type to variadic parameters, this type will be obsoleted. ////////////////////////////////////TICKET #987 : make lib::meta::Types<TYPES...> variadic