INFO: Tracking Brush Origins in a Win32-based Application |
Q102353
3.10 3.50 3.51 | 4.00 WINDOWS NT | WINDOWS kbgraphic
The information in this article applies to:
- Microsoft Win32 Application Programming Interface (API), used with:
- Microsoft Windows NT Server versions 3.1, 3.5, 3.51
- Microsoft Windows NT Workstation versions 3.1, 3.5, 3.51
- Microsoft Windows 4.0
- Microsoft Windows 95
SUMMARY
When writing to the Win32 API on Windows NT, it is no longer necessary to keep track of brush origins yourself. GDI32 keeps track of the brush origins by automatically recognizing when the origin has been changed. In Windows, you have to explicitly tell GDI to recognize the change by calling UnrealizeObject() with a handle to the brush. When a handle to a brush is passed to UnrealizeObject() in Windows NT, the function does nothing, therefore, it is still safe to call this API.
Win32s and Windows 95 require that you track the brush origins yourself, just as Windows 3.x does.
In Windows 3.1, the default brush origin is the screen origin. In Windows NT, the default origin is the client origin.
Additional query words: 3.10 4.00
Keywords : kbOSWinNT310 kbOSWinNT350 kbOSWinNT351 kbSDKWin32 kbOSWin95 kbDSupport
Issue type : kbinfo
Technology : kbAudDeveloper kbWin32sSearch kbWin32API
Last Reviewed: December 16, 2000 |