huh I forgot an entire part of a sentence. also added link to impulses |
m missed gallery oops |
||
(One intermediate revision by the same user not shown) | |||
Line 4: | Line 4: | ||
|Inputs= | |Inputs= | ||
[ | [ | ||
{"Name":"*", "Type":" | {"Name":"*", "Type":"Call"}, | ||
{"Name":"Target", "Type":"Slot"}, | {"Name":"Target", "Type":"Slot"}, | ||
{"Name":"SaveParent", "Type":"bool"}, | {"Name":"SaveParent", "Type":"bool"}, | ||
Line 54: | Line 54: | ||
== Examples == | == Examples == | ||
<gallery widths=480px heights=480px> | |||
File:ProtoFlux_example_undo_node_settup|This node being used in a set of nodes that undoes a bunch of actions that was done by a previous button | |||
</gallery> | |||
[[Category:ProtoFlux:Undo]] | [[Category:ProtoFlux:Undo]] |
Latest revision as of 19:37, 9 February 2024
The node will create an undo step in the context menu of the person who the impulse came from. The node will then send to the undo manager in the world the slot transforms that the slot provided into Target should revert to. Or in more simpler terms, the current transforms the provided Target (Slot) contains is what it will be reset to when undone via the context menu. Certain transforms will be included or omitted depending on booleans provided into the inputs.
when this node is paired with an Undo Batch, it's description if has one, will be ignored, and will be part of the Undo Batch's undo step instead.
Inputs
Input (Call)
Create the undo step and set the object to be despawned upon undoing to the slot provided.
Target (Slot)
The Slot which it's transforms will be undo able for this undo step.
SaveParent (Bool)
Whither to make the Slot's Parent undoable with this undo step.
SavePosition (Bool)
Whither to make the Slot's Position undoable with this undo step.
SaveRotation (Bool)
Whither to make the Slot's Rotation undoable with this undo step.
SaveScale (Bool)
Whither to make the Slot's Scale undoable with this undo step.
Outputs
Next (Continuation)
Continues to More undo steps, continues to code that eventually ends, or an End Undo Batch that continues to eventually ended code.
Examples
-
This node being used in a set of nodes that undoes a bunch of actions that was done by a previous button