| Previous | Next |
| UI_E_VALUE_NOT_DETERMINED | UI_E_BOOLEAN_EXPECTED |
UI_E_INVALID_OUTPUT
Within Windows Animation Manager, UI_E_INVALID_OUTPUT reports that a callback reported output that violated its interface contract. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.
Mechanism behind the code
Custom interpolation or priority callbacks participate in animation decisions through out parameters. S_OK is not enough when the returned values are invalid, nonfinite, outside the documented domain, or inconsistent with the accompanying result.
High-value telemetry
- Callback IID and method.
- All output parameters before return.
- Input values and animation time.
- Finite/range validation result.
Decision table
- 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 callback iid and method and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: initialize every out parameter on all branches. Hold constant: keep the original failing sample available for the final regression test.
Safe reduction procedure
Use a disposable control object, repository copy, file, or device association where the subsystem permits that safely.
- First: Initialize every out parameter on all branches.
- Next: Reject NaN, infinity, and domain violations before returning.
- Then: Test cancellation and failure branches separately.
- Finally: Use a minimal callback with constant valid output as a control.
Do not erase the distinction
During an investigation, UI_E_BOOLEAN_EXPECTED is specifically an invalid success HRESULT used as a Boolean; INVALID_OUTPUT concerns returned data.
Do not clamp silently unless the callback contract explicitly allows clamping.
Successful outcome
Verify it with the original scenario, one boundary case, and one deliberate failure; success means the callback passes explicit output validation for boundary, cancellation, and ordinary inputs.
Technical references
Looking for a different code? Search another status or error code.