public record class SettingsPageA settings page something other than the application contributed.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Doc 36 § D4's AddSettingsPage row, on P2's terms. A contribution kind is a record in the assembly that owns it and IEditorRegistry.Add is the whole surface — there is no method on PluginContext for this and there deliberately is not, because the alternative is a registry, a consumer and a plugin method per kind.
⚠ Here rather than in Vixen.Editor.Core, because a page is a SettingsCategory and that is the shell's. The registry keys on the static type it is handed and nothing about that type has to live where the registry does — SceneOverlay is in the scene view and CustomInspector is in the inspector for the same reason.
⚠ What reads it is EditorApplication, and it re-reads on IEditorRegistry.Changed. A plugin activating three seconds after start-up is always after a window was built, so a consumer that read the registry once would be one a plugin cannot reach — the failure RefreshAssetKinds and RefreshOverlays already exist to avoid. Withdrawing the contribution takes the page out of an open window through Remove.
Fields and properties (2)
public SettingsScope ScopeWhich window it goes in.
public SettingsCategory CategoryThe page itself: its id, its title, and what draws it.
Methods (1)
public SettingsPage(SettingsScope Scope, SettingsCategory Category)A settings page something other than the application contributed.
Used by (2)
- EditorApplicationVixen.Editor.App
- SettingsPageContributionTestsVixen.Editor.App.Tests