Maybe people could resign their useless “We want iOS” points to this feedback report from March 2013?
25108 - Xojo application is not retina display aware.
I know, that’s why I feel (some of) your pain. Even if you retinize Xojo, the icons and images obviously won’t be so it still looks a little naff.
[quote=149053:@Markus Winter]Maybe people could resign their useless “We want iOS” points to this feedback report from March 2013?
25108 - Xojo application is not retina display aware.
<https://xojo.com/issue/25108>[/quote]
Good idea, I will do just that.
I am a total Windows noob so what is a Manifest? Where is this file to be found?
It seems this is what needed to be added in the Manifest file:
<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>true</dpiAware>
</asmv3:windowsSettings>
</asmv3:application>
...
</assembly>
Done … its now on 35th place. 
The declare of Alain works but:
Some strange things happen:
Toolbar is half visible
Fonts are too small and when you enlarge them, they are clipped.
uploadimage
[quote=149049:@Alain Bailleul]Actually, I see there is a whole blog post on Xojo on DPI awareness and manifest editing:
http://www.xojo.com/blog/en/2013/11/writing-high-dpi-aware-windows-apps.php[/quote]
That is great ! William Yu is rather discrete, but always to the point. Quite a competent gentleman.
[quote=149056:@Christoph De Vocht]I am a total Windows noob so what is a Manifest? Where is this file to be found?
It seems this is what needed to be added in the Manifest file:
<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>true</dpiAware>
</asmv3:windowsSettings>
</asmv3:application>
...
</assembly>[/quote]
You should use the declare William posted. It is much faster. I shall look into PE Editor at a later date.
Yes, but potentially more dangerous if plugins are being used. Still think the manifest is the correct way to do it.
EDIT: Actually, the correct way would be that Xojo handles this for us. But I see there is already a case floating around this forum on that, so fingers crossed
Here are a few pointers :
https://duckduckgo.com/?q=portable+executable+editor
But this needs some experimentation I cannot conduct beyond looking at the manifest keys, since I do not have a high dpi screen.
Yes, MS also advices to use the manifest.
[quote=149053:@Markus Winter]Maybe people could resign their useless “We want iOS” points to this feedback report from March 2013?
25108 - Xojo application is not retina display aware.
Feedback Case #25108[/quote]
Done,
it is now on rang 28th.
OK. Just spent a few minutes looking at all the options to edit an executable manifest. The open source NetPE no longer works, if it ever did.
On MSDN, they promote PE Explorer, which is a $129.00 program that does that and many other things.
But the same publisher has another program for resources only called Resource Tuner that’s only $49.95 which allows editing the manifest very nicely.
See http://www.heaventools.com/download-resource-editor.htm
I played with the 30 days evaluation program. Is is pretty self-explanatory. Expand Manifest, click on the document, and you can edit the content in the text area on the right. Then save.
When installing, make sure to uncheck Add Resource Tuner to the context menu. It would add a pesky option to every right click menu on your system. I hate it when people do that.
doesn’t Visual Studio include an app to add an manifest to a file?
Of course best may be to have the framework be aware of HiDPI and help us by embedding a manifest allowing HiDPI right away?
[quote=149092:@Christian Schmitz]doesn’t Visual Studio include an app to add an manifest to a file?
Of course best may be to have the framework be aware of HiDPI and help us by embedding a manifest allowing HiDPI right away?[/quote]
As far as I know, the built in VS Manifest Editor is there only for applications that will be built with Visual Studio. I have used it for the apps I have in the Windows Store, but I do not see how it could be used to edit executables, as Resource Tuner does.
Ya slimy bar steward! I’m so waiting these to be available in Taiwan… I’ve been waiting for a 27" Retina display for years!
btw, just in case, I’m kidding with you, just very jealous!
HIDPI on Windows… MY GOD, I have a ‘Retina’ Sony Vaio. It’s horrible to use, not even MS apps are HIDPI aware, let alone any third party apps. I actually ended up using a non-retina resolution and just poking up with everything being blurry, it’s better than using it in HIDPI mode!
As you’ve found out, you though Retina on MacOS was hard…
[quote=149089:@Michel Bujardet]On MSDN, they promote PE Explorer, which is a $129.00 program that does that and many other things.
But the same publisher has another program for resources only called Resource Tuner that’s only $49.95 which allows editing the manifest very nicely.
[…]
[/quote]
You could use ResHack which is free http://www.angusj.com/resourcehacker/
Same with the Surface Pro 2 and 3. HiDPI is on by default and the font size is defaulted to 144%, but this confuses apps that require fullscreen display and many apps fail either stating that a larger display is required or simply by not starting.
Lots of complaints in the MSDN forums about the lack of a standard mechanism for handling this within an app.
There is one article that came out a while back, but it’s not satisfying what most are looking for.
I did not find it with a search. All the reasons why our collective knowledge sharing is so precious. Thank you Jrmie.
[quote=149351:@Tim Jones]Same with the Surface Pro 2 and 3. HiDPI is on by default and the font size is defaulted to 144%, but this confuses apps that require fullscreen display and many apps fail either stating that a larger display is required or simply by not starting.
Lots of complaints in the MSDN forums about the lack of a standard mechanism for handling this within an app.
There is one article that came out a while back, but it’s not satisfying what most are looking for.
Creating a DPI-Aware Application[/quote]
I echo this. Xojo is painful to use on the Surface Pro 3 because of the high DPI issues…