InputBindingData

Remarks

Composite parts are nested here rather than flattened into the binding list behind an isPartOfComposite flag, which is how Unity's asset stores them. The flat form makes every consumer reconstruct the tree, and makes a hand-edited file that reorders two lines mean something different — which is exactly the sort of breakage a text asset in version control must not have.

Fields and properties (7)

• public string Path

  The control, in InputControlPath syntax. Empty for a composite, whose value comes from its .

• public string? Name

  A display name for a rebinding screen, or .

• public string? Groups

  The control schemes this binding belongs to, semicolon-separated. or empty means every scheme.

• public string? Interactions

  The interactions, semicolon-separated, or .

• public string? Processors

  The processors, semicolon-separated, or .

• public InputCompositeKind Composite

  Which composite this is, or None.

• public IReadOnlyList<InputBindingPartData> Parts

  The composite's parts, or an empty list.

Methods (1)

• public InputBindingData(string Path, string? Name = null, string? Groups = null, string? Interactions = null, string? Processors = null, InputCompositeKind Composite = None, IReadOnlyList<InputBindingPartData>? Parts = null)

  One binding of an action, as the document holds it.

Used by (8)

• InputActionAssetReaderVixen.Input
• InputActionAssetTestsVixen.Input.Tests
• InputActionAssetWriterVixen.Input
• InputActionDataVixen.Input
• InputBindingVixen.Input
• AuthoringTestsVixen.Editor.AssetEditors.Tests
• InputActionsDocumentVixen.Editor.AssetEditors
• InputActionsViewVixen.Editor.AssetEditors