Not logged in▾
Log In Register
Forgot Password Resend Validation E-mail
In This Article

DPI Awareness

Actipro WinForms Controls have been designed to support applications configured for DPI awareness.

System Awareness vs. Per-Monitor Awareness

System DPI awareness means applications are configured to support the DPI of the primary monitor. If a window is moved to a monitor with a DPI that is different than the primary monitor, the operating system will render the application at system DPI and then scale the image to fit the DPI of the monitor. This can often lead to text and images that appear fuzzy. System DPI awareness works best in single-monitor scenarios or where all monitors are set to the same DPI.

Per-monitor DPI awareness means applications are configured to run on the DPI of the monitor where a window is displayed. If a window is moved to a monitor with a different DPI, the window will be rescaled and rendered at the DPI of the new monitor. This results in clear text and images at most DPI levels, although some images may still not scale with precision.

Tip

Per-monitor DPI awareness typically provides the best end-user experience and should be supported when possible.

Known Issues and Limitations

Actipro WinForms Controls target multiple .NET Frameworks, and each target can have drastically different levels of support for DPI awareness. These differences are most prevalent when working with per-monitor DPI awareness. When building DPI awareness for our controls, every effort has been made to support per-monitor DPI awareness, but some scenarios could not be consistently supported.

Tip

Per-monitor DPI awareness is still a work-in-progress for Windows Forms, so targeting the latest supported version of .NET is recommended.

Important

Actipro controls are tested with PerMonitorV2 only. The original PerMonitor configuration version was very limited and has been replaced with PerMonitorV2 on all versions of Windows still under support. For per-monitor DPI awareness, using PerMonitorV2 instead of PerMonitor is highly recommended.

Bars

  • The Bars customization form may not rescale correctly on some .NET targets when moving between monitors of different DPIs and the application is running with per-monitor DPI awareness. This primarily impacts .NET 6+.

Docking

  • DocumentMdiStyle.Standard may not properly clip the child window when maximized in a per-monitor DPI aware environment. If the monitor DPI is higher than the system DPI, part of the window chrome will be visible. If the monitor DPI is lower than the system DPI, part of the client area may be clipped. This issue can be mitigated by using DocumentMdiStyle.Tabbed instead.

SyntaxEditor

  • When using per-monitor DPI awareness and an instance of SyntaxEditor is display on more than one monitor with different DPIs, the common images used for IntelliPrompt may have a DPI that does not match the current monitor.