The event block a Custom graph node receives, and the callback types that take it. More...
Go to the source code of this file.
Classes | |
| struct | pulp::host::CustomNodeEventBlock |
| The events visible to one Custom node for one block. More... | |
Namespaces | |
| namespace | pulp |
| namespace | pulp::midi |
| namespace | pulp::host |
| Bounded event contracts shared by host ingress and graph-authored nodes. | |
Typedefs | |
| using | pulp::host::CustomNodeEventProcessFn |
| Stateless event-aware process callback. | |
| using | pulp::host::CustomNodeInstanceEventProcessFn |
| Stateful event-aware process callback. | |
The event block a Custom graph node receives, and the callback types that take it.
The graph has routed MIDI for a long time: gather_node_midi fans inbound events into per-node scratch for every node before the executor dispatches on binding kind, and a Processor wrapped by add_processor_node already consumes them. A Custom node was the one graph citizen whose binding never handed that scratch on. These types complete that lane; they do not add MIDI to the graph.
The block is a struct rather than a pair of arguments so that a later transport-aware or automation-aware event node is a new member here, not a fourth callback pair on CustomNodeType. It lives in its own header because custom_node_type.hpp is a reviewed public surface whose byte hash gates the capability fingerprint; keeping the vocabulary out of it holds that file's growth to the two callback members themselves.