| Previous | Next |
| TPC_S_TRUNCATED | TPC_S_NO_DATA_TO_PROCESS |
TPC_S_INTERRUPTED
Tablet PC recognition or training was interrupted
TPC_S_INTERRUPTED is HRESULT 262739 (0x00040253) from winerror.h. AllStat describes this result as “TabletPC inking error code; Recognition or training was interrupted.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The recognizer began work but recognition or training stopped before its normal completion.
Where the result is encountered
- This result can appear in foreground or background ink recognition; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in user-canceled training; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in application shutdown or stroke changes during recognition; record the producing interface and method rather than inferring behavior from the symbolic name alone.
The same numeric success value can be mishandled when a wrapper exposes only a Boolean. Keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
State boundary that must be proved
The central question for this HRESULT is whether the caller distinguishes intentional cancellation from recognizer failure and knows whether any partial personalization data was committed. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of it names the exact method contract, the object generation, and the outputs that remain valid. This prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Diagnostic sequence
- capture the raw HRESULT
0x00040253immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of it: interface, method, object instance, provider or filter version, thread or apartment, and operation phase.
- Validate the decisive contract boundary for this HRESULT: the caller distinguishes intentional cancellation from recognizer failure and knows whether any partial personalization data was committed.
- inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result.
- Compare the observed state before and after it; do not assume that a success severity bit means every optional sub-operation completed.
- reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
Evidence and telemetry to preserve
- preserve recognizer and context identity.
- preserve foreground versus background mode.
- preserve cancellation or shutdown source.
- preserve stroke collection generation.
- preserve completion event and partial result availability.
Also record tpc_s_interrupted_operation, tpc_s_interrupted_object, tpc_s_interrupted_state_before, tpc_s_interrupted_state_after, UTC time, process and thread identifiers, and a correlation ID. Keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Correct handling, retry, and recovery
Discard or label incomplete results according to the recognizer contract. Restart recognition only when the ink snapshot is stable and the user still needs the operation.
Retry it only when the recorded state can change the documented outcome. Repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Difference from nearby HRESULT values
TPC_S_NO_DATA_TO_PROCESS means no usable training input existed; it means work started and was stopped.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Practical validation scenario
A user edits strokes while background recognition is running. The application cancels the old context, receives it, and starts a new recognition pass against the updated stroke collection.
The negative test should preserve the condition that produces it; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
References
- Microsoft: COM success codes
- Microsoft: Pen input, ink, and recognition
- Microsoft: BackgroundRecognize
Looking for a different code? Search another status or error code.