State
State
Start here for AzState<T> creation, writes, subscriptions, scheduling, validation, binding, lifecycle, and API reference.
- Create and write
- Subscribe and bind
- Validate and schedule
- API reference
Use this section when a value has current meaning. State pages are split by how developers usually work: create/read/write first, then subscriptions, scheduling, validation, binding, lifecycle, advanced helpers, UI patterns, and API reference.
Create, Read, And WriteThe core AzState<T> model, initial values, comparers, Value, and SourceSet.Subscriptions And BindingSubscribe, SubscribeMap, SubscribeChanged, BindTo, and weak subscriptions.Scheduling And ValidationImmediate, NextUpdate, EndOfFrame, batching, validators, and TrySourceSet.Two-Way BindingReconcile state between UI and model without endless loops.Threading And LifecycleThread rules, token ownership, read-only exposure, reset, and cleanup.Advanced State HelpersObservability, AzDomainProperty<T>, and AzPipelinedState<T>.UI PatternsSlider binding, paired sliders, derived status state, and complete example.Pitfalls And APICommon mistakes, quick reference, and recommended defaults.
Recommended Reading Order
- Start with Create, Read, And Write.
- Use Subscriptions And Binding when connecting UI or model readers.
- Read Scheduling And Validation before relying on notification timing.
- Keep Pitfalls And API open while reviewing production code.