UtilitySetDocument

Remarks

The same arrangement BehaviorTreeDocument has — the model is Vixen.Editor.Ai's, the compiler is Vixen.Ai's, and this is the YAML end and the undo stack over it. Every gesture is one snapshot in, one snapshot out, and the entries merge so that dragging a curve parameter is one step rather than forty.

Fields and properties (6)

• public const string Extension

  What a utility set is written as.

• public string AssetPath

  Where the file is, absolute.

• public UtilitySetModel Model

  The set, and every operation over it.

• public string? LoadError

  Why the file would not read, or .

• public IReadOnlyList<BehaviorTreeDiagnostic> Diagnostics

  What the last Compile had to say.

• public UtilitySet? Set

  What the last Compile produced, or .

Events (1)

• public Action<UtilitySetDocument>? Changed

  Raised after anything changes the set.

Methods (5)

• public UtilitySetDocument(EditorProject project, AssetId asset, string path)

  Opens a set.

• public string ToYaml()

  The set as it would be written.

• public UtilitySet? Compile(BehaviorTreeResolver? resolver = null)

  Compiles the set, against whatever a caller can resolve.

• public void Edit(string name, Action<UtilitySetModel> gesture, string? mergeKey = null)

  Runs a gesture as one undo entry.

• protected override void SaveCore()

  Writes the document back to wherever it came from.

Used by (5)

• LiveUtilityTestsVixen.Editor.AssetEditors.Tests
• SnapshotCommandVixen.Editor.AssetEditors
• UtilitySetDocumentTestsVixen.Editor.AssetEditors.Tests
• UtilitySetEditorFactoryVixen.Editor.AssetEditors
• UtilitySetViewVixen.Editor.AssetEditors