Animation

Animation

Events use one global clock in seconds, including events in hidden spaces. Seeking evaluates the scene at the requested time instead of replaying every preceding frame.

An object event usually names object, start and duration. For example:

{
  "type": "Shift",
  "object": "plane.shape",
  "by": [2, 0],
  "start": 1,
  "duration": 2,
  "easing": "smooth"
}

This fragment requires an existing plane.shape. Top-level events default to start time zero; array order alone does not make them sequential. Entrance effects hide their targets before the entrance; exits hide them until a later entrance.

Supported families include creation/fades, movement, rotation/scaling, path transforms, parameter animation, emphasis overlays, camera events and space transforms. Capability restrictions vary by geometry: supporting an event does not imply that it works on text, meshes, groups and disconnected paths alike.

• EventGroup: run children together with local start offsets.
• Succession: run children sequentially.
• LaggedStart: stagger children.
• LaggedStartMap: apply a shared animation template to several targets.

A composition's explicit duration rescales its nested timing. Conflicting simultaneous property writers are rejected during compilation. Use exported supportedEvents and easingNames to discover supported names.

Available easing names: linear, smooth, ease-in, ease-out, smoother, sine-in, sine-out, sine-in-out, cubic-in, cubic-out, cubic-in-out, quart-in, quart-out, quart-in-out, quint-in, quint-out, quint-in-out, expo-in, expo-out, expo-in-out, circ-in, circ-out, circ-in-out.

Legacy documents

Use events, EventGroup, SceneEvent and supportedEvents in new documents. The compiler normalizes legacy animations and AnimationGroup JSON, but rejects both timeline keys in the same scope. The published schema describes canonical documents.

---

Wiki home · Quick start