DPI Aware PM Support

Post feature requests, product enhancement ideas, and other product-specific suggestions here. Do not post bug reports.
Forum rules
Do not post any licensing information in this forum.
This topic is 6 years and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Locked
User avatar
r41z0r
Posts: 8
Last visit: Sun Mar 04, 2018 10:36 pm

DPI Aware PM Support

Post by r41z0r »

Hey there,

I have a spimple request, since the beginning of Windows 8 more and more applications (compiled) need the feature to be DPI-Aware.

In Powershell Studio 2017 (act. Version) the predefined Manifest-Files from you set the DPI-Awareness only to "System-Aware" which results in the bad behavior for Windows 10, that you have to restart the application or have to logout and back onto Windows.... that is really bad.
To fix this behavior you just have to change your Mainfest-Line to:
  1. <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
  2.     <dpiAware>true/pm</dpiAware>
  3. </asmv3:windowsSettings>
Or even give the user another subsection, where he can set the DPI-Stuff for Manifest for himself.

It's really bad now to compile the application with an selfcontained Manifest, which is the same like yours only difference is the per Monitor Aware.

Look here for more information:
https://msdn.microsoft.com/en-us/librar ... x#dpiAware
User avatar
Alexander Riedel
Posts: 8478
Last visit: Tue Mar 26, 2024 8:52 am
Answers: 19
Been upvoted: 37 times

Re: DPI Aware PM Support

Post by Alexander Riedel »

You can define your own manifest at any time when packaging. It would help if you could define "bad behavior" (maybe with a screenshot) so we can try to replicate what you see and evalute possible options.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
r41z0r
Posts: 8
Last visit: Sun Mar 04, 2018 10:36 pm

Re: DPI Aware PM Support

Post by r41z0r »

Hello, thanks for the quick reply.

Attached is a screenshot of the problem.
You can see there, it's the Powershellstudio Manifest: "Embed a default manifest for elevation"
If you compile the script and make an *.exe File and open that with notepad++ you can see, that the dpi state is: <dpiAware>true</dpiaware>.
That only means, that the application is "System Aware" - You have to logout and login (Windows) to perform scaling.

But if you copy all that manifest content and change the line of dpiAware to "true/pm" it's per Monitor aware, so the scaling works just on the flow, you don't have to worry about anything.

Using a customManifest has the worse thing, that I need to worry about the Version etc.

Greetings,
Phil
Attachments
Manifest.png
Manifest.png (149.05 KiB) Viewed 5939 times
User avatar
Alexander Riedel
Posts: 8478
Last visit: Tue Mar 26, 2024 8:52 am
Answers: 19
Been upvoted: 37 times

Re: DPI Aware PM Support

Post by Alexander Riedel »

We will investigate if changing the default manifest will have ill effects on older machines before we can change anything.
Thank you for bringing it up.
Alexander Riedel
SAPIEN Technologies, Inc.
This topic is 6 years and 3 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Locked