Whether the processor runs. processKey skips processors with active: false.
Built-in processor id or custom name, unique in the pipeline and usable as an insertion target or for kick/activate toggles.
Priority — higher runs first. Processors sharing a weight form one stage; the stage runs as one unit, its members in insertion order.
Process one key event.
Snapshot of the engine state for this event.
true to consume the event and stop the pipeline,
false to pass it to the next processor.
A single stage in the keyboard event pipeline.
This is the runtime shape the engine stores: the fields beyond
idandprocessare stamped by the engine when a processor is registered, so callers never construct one of these directly — use ProcessorInput with KeyboardEngine.addProcessor and let the engine fill the rest.Each processor evaluates whether it should handle the current event. If it consumes the event it returns
trueand the chain stops; otherwise it returnsfalseto pass the event to the next processor.Example