Why Did My DPI-Unaware Application Suddenly Become DPI-Aware?

Unexpected DPI-Aware Behavior in Application Updates

A previously DPI-unaware application unexpectedly became DPI-aware in a later release, causing UI problems. Despite lacking explicit DPI settings in the application manifest, and relying on Windows bitmap scaling, the application's DPI handling changed between versions. This investigation reveals that third-party libraries may be responsible for this shift.

DPI Awareness Explained

Windows DPI awareness dictates how an application adapts to different screen resolutions and scaling factors. It ensures UI clarity across various displays. DPI-unaware applications depend on Windows scaling, while DPI-aware applications manage scaling internally.

Root Cause Analysis: The Role of Third-Party Components

The assumption that the absence of DPI settings in app.manifest defaults to DPI-unaware is incorrect. Including DPI-aware third-party components can override this, making the entire application DPI-aware unless explicitly prevented.

Solutions for Restoring DPI-Unaware Behavior

To revert to DPI-unaware mode, try these solutions:

• Modify the Application Manifest: Explicitly set <dpiaware> to false in the application manifest file.
• Use Windows APIs: Employ Windows API calls like SetProcessDPIAware or SetProcessDpiAwarenessContext to force DPI-unaware behavior.
• Disable Automatic DPI Adjustment: Add the [assembly: System.Windows.Media.DisableDpiAwareness] attribute to AssemblyInfo.cs to prevent third-party components from automatically enabling DPI awareness.

These methods provide manual control over the application's DPI awareness, ensuring consistent behavior.

The above is the detailed content of Why Did My DPI-Unaware Application Suddenly Become DPI-Aware?. For more information, please follow other related articles on the PHP Chinese website!