Ichthyostega
4fa18cf1d2
One of the goals of this extended clean-up and refactoring is to allow access to the data buffers of a `DataSink` through a `BuffHandle` as front-end. Which essentially means that the ''Buffer Provider Protocol'' and the ''Output Slot Protocol'' mesh together well. After the clean-up of the `BufferProvider` implementation hierarchy, the viability of this idea was demonstrated with the `BufferProxyAdapter` draft; so it is now roughly clear what must be changed within the existing implementation of `OutputSlot`. More specifically, the only actual implementation ever completed was a dummy implementation for test (`DiagnosticOutputSlot`), which hooked confusingly into the corresponding dummy implementation of `BufferProvider`, that was written one year earlier (and was also without actual implementation at that time). So the second half of the task ahead seems very similar to the first part: - the base implementation of the ''Output Slot Protocol'' seems roughly acceptable - but the actual dummy implementation was somewhat confused and should be re-written from scratch, without ''any attempt to cut corners by re-using other dummy code'' __Note__ as part of this analysis I discovered some gap in the design regarding timeout handling ⟶ Ticket #1417 |
||
|---|---|---|
| .. | ||
| asset | ||
| control | ||
| engine | ||
| fixture | ||
| mobject | ||
| play | ||
| test | ||
| DIR_INFO | ||
| render-segment-test.cpp | ||