public sealed class PriorityLadderContentThe names a project's authors pick priorities from.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
⚠ Two reasons this is data rather than sugar, and neither is presentation. A raw integer has no meaning across a project, so two authors pick 70 and 700 for the same intent and the arbitration between their clips is an accident. And the right ladder is domain-specific — the ordering that makes sense for characters swimming is not the one for characters driving — so it is a file with aliases rather than an enum in the engine, and one project may name several and say which applies where.
A sub-step within a rung is what lets two contacts at the same level be ordered without inventing a rung: contact and contact+1 resolve to adjacent integers and read as the same intent, which is what an author means when they say one grip matters slightly more than another.
Fields and properties (8)
public const int CurrentThe version this build writes.
public const string ExtensionThe file extension.
public int VersionWhich version of the format wrote it.
public string NameWhat the ladder is called.
public int StepHow far apart two adjacent rungs are, so a sub-step has room between them.
public PriorityRungRecord[] RungsThe rungs, lowest first.
public Dictionary<string, string> ExtensionsMarkup this build did not interpret.
public static PriorityLadderContent DefaultThe ladder every project gets before it declares one of its own.
Methods (1)
public PriorityLadder Bake()Turns it into the lookup a bake uses.
Used by (6)
- PriorityLadderVixen.Animation
- TypeRegistrationVixen.Animation
- Vixen_Animation_Constraints_PriorityLadderContentSerializerVixen.Animation
- AnimationBinderVixen.Editor.AssetEditors
- ConstraintAuthoringImporterTestsVixen.Editor.Assets.Tests
- PriorityLadderImporterVixen.Editor.Assets