public enum StyleOriginWho a declaration came from, which is the cascade's first question.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
The order here is the order of increasing power for normal declarations, and the cascade reverses it for !important ones. That reversal is the whole point of the mechanism: a user stylesheet marking something important is a user who means it, and it has to be able to beat a page that also means it — an accessibility guarantee rather than a curiosity, and the reason importance is not simply "wins".
Vixen has all three. The engine's own control themes are UserAgent, a game's stylesheets are Author, and User is what a player's accessibility overrides load as.
Fields and properties (3)
UserAgentVixen's built-in styles for its own controls.
UserA player's own overrides.
AuthorThe game's stylesheets. Where nearly everything lives.
Used by (21)
- AdvancedThemeVixen.Ui.Controls.Advanced
- CascadeFixtureVixen.Ui.Styling.Tests
- CascadeOrderTestsVixen.Ui.Styling.Tests
- CascadeRanksVixen.Ui.Styling
- ControlThemeVixen.Ui.Controls
- SheetVixen.Ui.Styling
- StyleEngineVixen.Ui.Styling
- StyleRuleVixen.Ui.Styling
- StyleRuleSetVixen.Ui.Styling
- StyleSheetLoaderVixen.Ui.Styling
- UiDocumentVixen.Ui
- UtilityFixtureVixen.Ui.Styling.Utilities.Tests
- AssetEditorThemeVixen.Editor.AssetEditors
- BrowserThemeVixen.Editor.Inspector
- DebuggerThemeVixen.Editor.Debugger
- EditorThemeVixen.Editor.Ui
- InspectorThemeVixen.Editor.Inspector
- NodeGraphThemeVixen.Editor.NodeGraph
- PreviewCodeEditorViewVixen.Editor.AssetEditors
- ProfilerThemeVixen.Editor.Profiler
- WorldThemeVixen.Editor.App