| Previous | Next |
| UI_E_INVALID_DIMENSION | UI_E_WINDOW_CLOSED |
UI_E_PRIMITIVE_OUT_OF_BOUNDS
The scope of UI_E_PRIMITIVE_OUT_OF_BOUNDS is Windows Animation Manager: an interpolation primitive begins at or beyond the interpolator duration. Preserve 0x802A010C beside the returning call before cleanup or retry creates a more generic secondary failure.
Read the condition first
A custom interpolator is a timed sequence of primitives. A primitive positioned outside the total duration cannot contribute a valid interval, even if its own parameters are numerically valid.
Keep neighboring conditions separate
UI_E_FP_OVERFLOW is numeric range failure; OUT_OF_BOUNDS is a finite but invalid timeline position.
Do not extend total duration automatically without confirming the intended animation semantics.
Incident record
- Primitive start time.
- Total interpolator duration.
- Primitive duration and order.
- Unit conversion and accumulated offsets.
Reproduce without destroying evidence
The investigation should change one variable at a time and keep the original failing sample.
- First: Compute cumulative offsets before adding primitives.
- Next: Use a single primitive starting at zero.
- Then: Check strict less-than bounds at the endpoint.
- Finally: Test zero-duration and exact-end cases explicitly.
Three useful controls
- Fresh storyboard or animation object: a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: keep the timeline, transitions, and manager version fixed.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: retain primitive start time and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: compute cumulative offsets before adding primitives. Hold constant: keep the original failing sample available for the final regression test.
Definition of done
Closure requires every primitive occupies a valid interval within the interpolator and endpoint tests have explicit expected results; then repeat the next lifecycle operation to detect stale state.
Technical references
The references below define the API family or storage/protocol behavior used to interpret this result.
Looking for a different code? Search another status or error code.