| Previous | Next |
| ERROR_TRANSFORM_NOT_SUPPORTED | ERROR_INVALID_CMM |
ERROR_CLIPPING_NOT_SUPPORTED
The requested clipping operation is unsupported.
ERROR_CLIPPING_NOT_SUPPORTED is Win32 error 2005 (0x7D5). Clipping combines visible regions, selected clip regions, paths, transforms, and device limits to decide where drawing is allowed. The code indicates that the current DC, driver, metafile path, or requested region operation cannot represent the clip.
Operations that expose the limitation
- a complex path or region is selected into a printer or compatibility DC with limited clipping support
- the requested combine mode or transformed region creates complexity beyond the driver or export format
- metafile playback or conversion cannot reproduce the original clip records
- coordinates overflow device-region limits after scaling or world transformation
- application code applies clipping to an information DC or another DC type that is not a drawing destination
Clipping evidence to record
Capture the clipping API and combine mode, region type and rectangle count, path complexity, coordinate bounds, current world transform and mapping mode, DC technology, driver/version, metafile status, and return values from GetClipBox or region queries. Avoid dumping huge region data into normal logs; store a bounded sample or hash and a reproducible test asset.
How to isolate the unsupported feature
Reset to no application clip and verify basic drawing. Then test a rectangular region, a small polygonal region, the actual path, and each combine mode. Compare the same sequence on a display DC and the destination printer/export DC.
Check transformed bounds for overflow and simplify self-intersecting or extremely detailed paths. If the failure occurs during metafile playback, enumerate records and locate the clip-changing record before blaming unrelated drawing content.
Recovery and fallback
Replace the clip with a simpler region, pre-clip geometry, split rendering into rectangular bands, or rasterize the affected portion. For printers, update the driver only after a second driver or device proves the issue is implementation-specific.
Bound region complexity in document importers, keep DC state balanced with SaveDC/RestoreDC, and test clipping under transforms. A fallback should preserve security boundaries if clipping is used to hide sensitive content; never silently draw unclipped output.
Difference from an empty clip region
An empty valid clip simply suppresses drawing and may not be an error. Error 2005 means the clipping operation itself cannot be supported or represented in the current rendering path.
Example
A CAD print job selects a region containing tens of thousands of transformed edges. Display rendering works, but the printer driver returns 2005. Tiling the page and simplifying each clip region allows printing without removing the intended boundaries.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: Clipping
- Microsoft: ExtSelectClipRgn
Looking for a different code? Search another status or error code.