Slot Children Events (LogiX node)
| Slot Children Events | ||
|---|---|---|
 | ||
| Inputs | ||
| Slot | Instance | |
| User | OnUser | |
| Outputs | ||
| Impulse | OnChildAdded | |
| Impulse | OnChildRemoved | |
| Slot | Child | |
The Slot Children Events node generates impulses when child slots are added or removed from the Instance slot.
Note that currently Slot Children Events does not support the value of the Instance slot changing. [1]
Usage
The OnUser input can be used to specify which user will own the generated impulses. By default impulses are owned by the user who caused the change. Providing the Local User to this input will result in impulses being fired for all users in the session.
The OnChildAdded output fires impulses whenever a child slot is added under the Instance slot.
The OnChildRemoved output fires impulses whenever a child slot is removed from under the Instance slot.
The Child output provides the slot which was added / removed from under the Instance slot. This value is only available for the duration of the impulse chain started by OnChildAdded or OnChildRemoved. Note that the value will be null if a child slot is destroyed, rather than being reparented away from the Instance slot.
Examples
Tutorial by ProbablePrime:
Related Issues
#666 - Bugs with Slot Children Events node
#930 - Add OnChildDestroyed to Slot Children Events node
#1014 - Slot Children Events causing null parents on deletion
#1335 - Slot Child Events Bug: event is too fast?
#2822 - Slot Children Events node breaks on input change