veloxdev-create-animation

Call Transition<T>.Create(), chain one .Property(path, endValue) per line, and finish with .Effect(new TransitionEffect { ... }) to set duration and easing. Execute it with transition.Execute(target); the call returns immediately while the animation runs asynchronously.

Reference exactly one adapter package matching your GUI: VeloxDev.WPF, VeloxDev.Avalonia, VeloxDev.WinUI, VeloxDev.MAUI, VeloxDev.WinForms, VeloxDev.Razor, or VeloxDev.Jalium. The adapter brings VeloxDev.Core in transitively, so no additional reference is needed.

Cache it in a static readonly field when the shape and endpoint are identical every run; create and discard it at the call site when the endpoint is computed per call. Never cache a declaration that captures a local, since the captured value becomes shared across all later executions.

The most common cause is an out-of-range index in the property path, which silently skips the frame with no exception or log. Also check that a second mutual animation on the same target has not cancelled the first, since Execute supersedes running animations by default.

Yes, by building a custom adapter that implements a UIThreadInspector, platform samplers, and registration against Core's interfaces, as documented in references/adapter.md. Start from the shipped adapter whose host most resembles yours rather than from the raw interfaces.

A live index like Items[t.Selected] is re-evaluated every frame and follows changes mid-flight, while PathIndex.Frozen(t.Selected) is read once when the segment starts and stays anchored. Freeze when the end value must land in the same slot it was read from.