Lumiera
0.pre.03
»edit your freedom«
|
#include "steam/engine/connectivity-obsolete.hpp"
Key abstraction of the Render Engine: A Data processing Node.
it's not clear as of 9/09 if ProcNode shall be an ABC/Interface It might be used as ABC (as was the original intention) when implementing several query/information functions. In that case, the ctor will become protected. The alternative would be to push down these information-retrieval part into a configurable element within Connectivity, in which case we even might drop ProcNode as a frontend entirely.
WIP-WIP-WIP 2024 Node-Invocation is reworked from ground up for the »Playback Vertical Slice«
Definition at line 142 of file connectivity-obsolete.hpp.
Public Member Functions | |
ProcNode_Obsolete (Connectivity const &wd) | |
bool | isValid () const |
uint | nrO () |
output channel count | |
BuffHandle | pull (StateClosure_OBSOLETE ¤tProcess, uint requestedOutputNr=0) const |
Engine Core operation: render and pull output from this node. More... | |
Private Types | |
typedef mobject::Parameter< double > | Param |
Private Attributes | |
vector< Param > | params |
const Connectivity & | wiringConfig_ |
Additional Inherited Members | |
Private Member Functions inherited from NonCopyable | |
NonCopyable (NonCopyable const &)=delete | |
NonCopyable & | operator= (NonCopyable const &)=delete |
|
inline |
Engine Core operation: render and pull output from this node.
On return, currentProcess will hold onto output buffer(s) containing the calculated result frames. In case this node calculates a multichannel output, only one channel can be retrieved by such a pull()
call, but you can expect data of the other channels to be processed and fed to cache.
currentProcess | the current processing state for managing buffers and accessing current parameter values |
requestedOutputNr | the output channel requested (in case this node delivers more than one output channel) |
Definition at line 182 of file connectivity-obsolete.hpp.
References Connectivity::callDown().