KeyMapPresets

Remarks

⚠ Doc 20: "A Unity user and an Unreal user disagree about what W does and both are certain." They happen to agree about W — both put Translate there — and disagree about almost everything around it: Play is Ctrl+P in one and Alt+P in the other, Duplicate is Ctrl+D in one and Ctrl+W in the other, and Save All is under two different modifiers. Shipping the three converts a week of friction into a dropdown.

⚠ Vixen's own preset is empty, and that is not a stub. The shipped defaults are the Vixen keymap — they are declared beside the commands, where a default belongs — so a preset that restated them would be a second copy of the same table, and the way that goes wrong is a default moved in one place and not the other. Choosing "Vixen" means "no layer", which is exactly what it should mean.

⚠ A preset only ever moves keys that would otherwise collide, or that the other editor genuinely puts somewhere else. Every entry below either matches what that editor does or vacates a chord the same preset gives to something else — Unity's Ctrl+P is Play, so the palette has to move, and Unreal's Ctrl+W is Duplicate, so Close Panel has to. A preset that moved a key for neither reason would be a preset nobody can predict.

Fields and properties (4)

• public const string Vixen

  The editor's own bindings, which is the absence of a preset.

• public const string Unity

  Unity's, as far as the commands that exist allow.

• public const string Unreal

  Unreal's, on the same terms.

• public static IReadOnlyList<string> Names

  Every preset this assembly ships, in the order a dropdown should offer them.

Methods (1)

• public static KeyMapPreset? Find(string? name)

  The preset with a name, or if this assembly has none.

Used by (5)

• KeyBindingsPanelTestsVixen.Editor.App.Tests
• KeyBindingsViewVixen.Editor.Ui
• KeyMapVixen.Editor.Ui
• KeyMapPresetTestsVixen.Editor.Ui.Tests
• MilestoneE3TestsVixen.Editor.App.Tests