The TriggerSequence Editor configures a TriggerSequence function entity: an ordered list of other entities to fire, optional delays between them, and the start / finished method names that become pins on the flowgraph node.
Entity parameters such as trigger_mode, use_random_intervals, and interval_multiplier stay in the Entity Inspector. This editor only edits the sequence list and method entries stored on the entity.
TriggerSequence entity in the composite list or flowgraph.Edits apply directly to the selected entity while the window is open. The window closes if you reload commands, select a different entity, or switch composite.
The window is split horizontally:
Drag the splitter between the panels to resize. Close is in the bottom-right corner.
The Entities list shows each sequence entry as a row: the resolved entity hierarchy path, and the delay in seconds. Checkboxes on the left are used for bulk removal.
Click Add Entities… to open the hierarchy picker with checkboxes. Check one or more function entities (you can still follow into nested composites first), then confirm. All checked entities are inserted after the current selection (or at the end if nothing is selected). If nothing is checked, the highlighted row alone is added.
Selecting a row shows the details panel:
trigger_mode and related parameters).The Triggers list is the set of start / end parameters this TriggerSequence exposes. Each line shows method -> method_finished.
These methods apply to all entities in the Entities list — when the sequence runs a method, every target is triggered with that method name (with its own delay).
For a parameter name X, the editor stores three related identifiers that appear as pins on the flowgraph node:
X — input method (start)X_relay — relay outputX_finished — finished outputAfter adding or renaming methods, refresh or reselect the node on the flowgraph if pin lists look stale. Standard methods like proxy_enable / proxy_disable remain on the entity type itself; the Triggers list is for the extra sequence methods you define here.
Click Close to leave the editor. Before closing, OpenCAGE checks that every sequence entry points at a real entity hierarchy. If any entry is empty or incomplete, you get an error and the window stays open so you can fix it.
There is no separate Save button — sequence and method edits are already on the entity. Persist them with the usual composite / level save.