| Previous | Next |
| DRAGDROP_S_CANCEL | VFW_S_NO_MORE_ITEMS |
DRAGDROP_S_USEDEFAULTCURSORS
Use OLE default drag cursors
DRAGDROP_S_USEDEFAULTCURSORS is HRESULT 262402 (0x00040102) from winerror.h. AllStat describes this result as “Use the default cursor.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The drag source feedback callback succeeded and asks OLE to display its standard cursor for the current drop effect.
State boundary that must be proved
The central question for it is whether the current effect value is accurate and the source has not installed a custom cursor that it expects to remain active. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of this result 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.
Where the result is encountered
- This result can appear in IDropSource::GiveFeedback implementations; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in applications that customize only some drag effects; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in drag operations where OLE owns cursor selection; 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.
Evidence and telemetry to preserve
- preserve current DROPEFFECT flags.
- preserve GiveFeedback call sequence.
- preserve target transitions and modifier keys.
- preserve custom cursor handles if any.
- preserve DPI and theme conditions affecting cursor presentation.
Also record dragdrop_s_usedefaultcursors_operation, dragdrop_s_usedefaultcursors_object, dragdrop_s_usedefaultcursors_state_before, dragdrop_s_usedefaultcursors_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.
Diagnostic sequence
- capture the raw HRESULT
0x00040102immediately 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 it: the current effect value is accurate and the source has not installed a custom cursor that it expects to remain active.
- 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.
Correct handling, retry, and recovery
Return the status intentionally when default feedback is desired. Do not treat it as the final result of DoDragDrop or as evidence that a target accepted the data.
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.
Practical validation scenario
A source uses a custom cursor for a proprietary link effect but standard cursors for copy and move. GiveFeedback returns it for copy, allowing OLE to keep cursor behavior consistent.
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.
Difference from nearby HRESULT values
DRAGDROP_S_DROP and DRAGDROP_S_CANCEL terminate the drag loop; it only controls feedback while the loop continues.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Developer and administrator guidance
Code handling it should test the exact documented value before a generic SUCCEEDED(hr) branch when outputs or control flow differ. Operational remediation for it should target the owning COM, media, Tablet PC, or OLE DB component instead of resetting unrelated services.
A support report for it should include decimal 262402, hexadecimal 0x00040102, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
Looking for a different code? Search another status or error code.