Good day!
I've been working on a WPF app for some time now (as a learning experience and oh boy it was a learning experience) and it's finally ready for release. Release means installing it on my HTPC where it will be used to browse my movie collection.
I designed it on my PC which runs 1920*1080 but at the normal DPI setting, while the HTPC/TV is running at the same resolution but a higher DPI setting for obvious reasons.
The problem is my app goes bonkers on the HTPC, messing up pretty much everything as far as visuals go. I know this is due to bad design (mea culpa), but since it's an application that will only be used by me I'm looking for an quick fix, not a full redesign. I read it would be possible to stop the app from being DPI aware by adding the following to AssemblyInfo.cs:
[assembly: System.Windows.Media.DisableDpiAwareness]
However, it doesn't seem to have any effect and the behavior of the app remains the same.
Could anyone point me in the right direction?
Thank you, Johan
Choose Tools > Options to open the Options dialog. In the Options dialog, choose Windows Forms Designer > General, and set DPI Scaling Notifications to False.
Windows Presentation Foundation (WPF) applications are by default system DPI-aware.
Select Display > Change the size of text, apps, and other items, and then adjust the slider for each monitor. Right-click the application, select Properties, select the Compatibility tab, and then select the Disable display scaling on high DPI settings check box.
The DPI Awareness Mode specifies the way an application is displayed when shown on a high resolution screen. Unaware. This mode works on all Windows versions prior to Windows Vista. In this mode, applications assume that all displays have the default 96 DPI (100%) scaling.
Just some ideas (not tried):
Are you running on XP? That option might not work on that platform.
What follows are probably just different ways to set the same DpiAwareness option:
look at the "compatibility mode" settings on your EXE...right click it's properties...and turn on "Disable display scaling"
create a manifest, and say you aren't aware
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" > ... <asmv3:application> <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings"> <dpiAware>false</dpiAware> </asmv3:windowsSettings> </asmv3:application> ... </assembly>
call SetProcessDPIAware
(think you have to call this early i.e. before Window is created)
http://msdn.microsoft.com/en-gb/library/windows/desktop/ms633543(v=vs.85).aspx
You can call IsProcessDPIAware
to check if your apps process has had the setting applied to it or not.
Here's how you find out what DPI you are currently using:
Access CompositionTarget
via the PresentationSource
of your Window
to find out what DPI scaling it's using.....you can then use the values to do some scaling adjustments i.e. scale down your "stuff" (whose sizes/length/etc are specified in Device Independent Units), so that when its scaled up due to a higher DPI being in effect it doesn't explode the physical pixel usage (...this can be done in various ways e.g. ViewBox
, or calculations on widths, etc on elements ).
double dpiX, double dpiY; PresentationSource presentationsource = PresentationSource.FromVisual(mywindow); if (presentationsource != null) // make sure it's connected { dpiX = 96.0 * presentationsource.CompositionTarget.TransformToDevice.M11; dpiY = 96.0 * presentationsource.CompositionTarget.TransformToDevice.M22; }
use the ViewBox
trick
See this answer I made before that allowed a Canvas
to use positions that were interpreted as "native" pixel no matter what the DPI scaling.
WPF for LCD screen Full HD
access the TransFormToDevice
scaling matrix on the CompositionTarget
, and from that calculate a new matrix that just undoes that scaling and use that in LayoutTransform
or RenderTransform
.
use a method (maybe even put it in a Converter) that modifies a DIP (Device Independent Position) position/length on an explicit basis....you might do that if you want your Window Size to match a particular pixel size.
This blog article explains how to use a Decorator subclass to do just that.
In short, create a class like this:
namespace MyNamespace
{
public class DpiDecorator : Decorator
{
public DpiDecorator()
{
this.Loaded += (s, e) =>
{
Matrix m = PresentationSource.FromVisual(this).CompositionTarget.TransformToDevice;
ScaleTransform dpiTransform = new ScaleTransform(1 / m.M11, 1 / m.M22);
if (dpiTransform.CanFreeze)
dpiTransform.Freeze();
this.LayoutTransform = dpiTransform;
};
}
};
};
Then add something like xmlns:custom="clr-namespace:MyNamespace"
to your top-level window definition, then enclose your DPI-independent user-interface with <custom:DpiDecorator>
...</custom:DpiDecorator>
.
None of the above truly disable the dpi scaling in WPF.
This is how dpi scaling is calculated in .net 4.6 by WPF: 1) HwndTarget which is the CompositionTarget used by all visuals. 2) UIElement which is the base class for visuals and the place where dpi scaling calculation results are stored.
WPF makes sure the global scaling is calculated once when first visual is prepared. This is controlled by a boolean on HwndTarget {private static bool _setDpi = true}. After calculating the dpi, the _setDpi field is set to false and dpi aware methods are shortcut using code like this {if (!HwndTarget._setDpi) return;}
A similar thing happens for every UIElement, which has the same pattern using {private static bool _setDpi = true} to allow calculation first time.
Next check comes from ProcessDpiAwareness which can be None, Process, or Monitor. In order to stop WPF from considering individual monitors you needs to set ProcessDpiAwareness to Process (int 1).
Finally when dpi is calculated the result is stored in 2 lists called DpiScaleXValues and DpiScaleYValues on UIElement. So you need to initialize these to correct values.
Here is a sample code I use for myself (only works for .net 4.6):
var setDpiHwnd = typeof(HwndTarget).GetField("_setDpi", BindingFlags.Static | BindingFlags.NonPublic);
setDpiHwnd?.SetValue(null, false);
var setProcessDpiAwareness = typeof(HwndTarget).GetProperty("ProcessDpiAwareness", BindingFlags.Static | BindingFlags.NonPublic);
setProcessDpiAwareness?.SetValue(null, 1, null);
var setDpi = typeof(UIElement).GetField("_setDpi", BindingFlags.Static | BindingFlags.NonPublic);
setDpi?.SetValue(null, false);
var setDpiXValues = (List<double>)typeof(UIElement).GetField("DpiScaleXValues", BindingFlags.Static | BindingFlags.NonPublic)?.GetValue(null);
setDpiXValues?.Insert(0, 1);
var setDpiYValues = (List<double>)typeof(UIElement).GetField("DpiScaleYValues", BindingFlags.Static | BindingFlags.NonPublic)?.GetValue(null);
setDpiYValues?.Insert(0, 1);
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With