public sealed class TransformTargetsCommandOne gizmo drag, as something the undo stack can take back.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Recorded on mouse-up, from what the gizmo captured on mouse-down. A command per frame of the drag would work — they would merge — but it would mean allocating and executing three hundred commands to move one crate, and every one of them would re-apply a transform the gizmo had already applied. The gizmo owns the live manipulation and this owns the history, which is the same division CommandTransaction makes for a drag somebody else is driving.
Position, rotation and scale together, per target. A rotate about a group's centre moves every object as well as turning it, and three separate commands for one drag would be three undo steps that only make sense applied together.
Fields and properties (2)
public string NameWhat this is called in the undo history, as a person would say it.
public bool IsEmptyWhether the drag changed anything at all.
Methods (4)
public TransformTargetsCommand(string name, IReadOnlyList<IGizmoTarget> targets, IReadOnlyList<(Vector3 Position, Quaternion Rotation, Vector3 Scale)> before, EditorDocument? document = null)Describes a drag that has already happened.
public void Do(EditorContext context)Applies the change.
public void Undo(EditorContext context)Puts back exactly what Do changed.
public bool TryMergeWith(IEditorCommand previous, out IEditorCommand? merged)
Used by (1)
- EntityGizmoTargetVixen.Editor.SceneView