Desktop Management
A display driver must implement DrvAssertMode and DrvGetModes to manage desktops.
If the display driver is palette-managed, it will also receive a call to DrvSetPalette to reset its palette to the correct state.
GDI's mechanism for handling dynamic mode changes has changed significantly in Windows 2000 and later operating system versions. The GDI HDEV assigned to a driver during initialization may differ from the HDEV assigned after the mode change is complete. Display drivers will generally be unaffected by this change for the following reasons:
Drivers have always assigned ppdev->hdevEng = hdev in their DrvCompletePDEV implementations.
Drivers have always referenced ppdev->hdevEng in any callbacks that require an HDEV.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for