| Previous | Next |
| INPUT_E_FRAME | INPUT_E_DEVICE_INFO |
INPUT_E_HISTORY
INPUT_E_HISTORY belongs to pointer packet, frame, and history validation. A sequence of pointer frames is internally inconsistent across time. The diagnostic goal for it is to identify the first rejecting object and transition, not merely the final high-level symptom.
Locate the first rejecting layer
Windows validates input at several nested levels., a packet describes one pointer observation, a frame groups simultaneous observations, and history links frames over time. The diagnostic task is to locate the first level at which identity, flags, timing, device information, or lifecycle becomes inconsistent; repairing only the last packet can leave an invalid frame or history chain unchanged.
Inspect the following boundary: history validation spans frame boundaries. Pointer identity, type, source device, frame IDs, timestamps, and DOWN/UPDATE/UP lifecycle must remain coherent throughout the sequence.
Evidence that changes the diagnosis
| Record | Why it matters here |
|---|---|
| All frames in original order, not only the final frame | Recording all frames in original order, not only the final frame separates the pointer packet, frame, and history validation boundary from a later wrapper symptom. |
| Per-pointer lifecycle timeline and source device | In this result diagnostics, recording per-pointer lifecycle timeline and source device ties the HRESULT to the pointer packet, frame, and history validation boundary rather than to the final visible failure. |
| Frame IDs and timestamps before and after coalescing | Comparing frame IDs and timestamps before and after coalescing shows whether this result follows input, object state, or environment. |
| History retrieval counts and buffer sizing results | Preserving history retrieval counts and buffer sizing results provides the evidence needed to test this distinction: iNPUT_E_OUT_OF_ORDER is limited to nonchronological data; this result also covers duplicate frame IDs and identity changes even when timestamps increase. |
Controlled reproduction
Capture the submitted structures before Windows modifies counts or output buffers. Reduce the sequence from history to one frame and then to one packet while preserving the original pointer IDs, flags, and time base so the level that first fails remains observable.
- replay one pointer history without coalescing.
- When it is returned, add coalesced frames in documented chronological order.
- Confirm that frame IDs are unique and timestamps do not regress.
- verify that a pointer does not change type or device before its lifetime ends.
Comparison tests
| Test | Interpretation | Hold constant |
|---|---|---|
| Same environment, reduced input | If this result disappears with a smaller faithful case, complexity within pointer packet, frame, and history validation is implicated. | Keep all frames in original order, not only the final frame fixed while simplifying frame IDs and timestamps before and after coalescing. |
| Same input, fresh object generation | If it changes after rebuilding state, examine ownership across the packet producer, frame collector, and interaction consumer. | Place per-pointer lifecycle timeline and source device on the timeline of the last successful transition. |
| Same operation on a controlled second path | If it follows one environment, the failure is not explained by source data alone. | Compare pointer type, device identity, window, DPI context, and callback phase while preserving history retrieval counts and buffer sizing results. |
Misleading responses
INPUT_E_OUT_OF_ORDER is limited to nonchronological data; it also covers duplicate frame IDs and identity changes even when timestamps increase. Do not discard intermediate history to make the latest point work. That can break gesture velocity, handwriting, and cancellation semantics.
Closure criteria
A correction for it should let the operation at the pointer packet, frame, and history validation boundary complete repeatedly under the original supported conditions. Repeat the control that begins with “Replay one pointer history without coalescing” and confirm that the following lifecycle step also succeeds. Keep the original failing sample and one deliberate negative case so fallback cannot be mistaken for repair.
Technical references
When it is returned, these references define the public API family, object model, or error list used to interpret this status.
- Microsoft: COM error codes for Input and graphics.
- Microsoft: Pointer Input Messages and Notifications.
- Microsoft: POINTER_INFO structure and pointer lifetime.
- Microsoft: GetPointerFrameInfoHistory.
- Microsoft: Interaction Context API.
Looking for a different code? Search another status or error code.