You are here

Home » Forums » General Forums » General Discussion

Platform ignores .manifest files

8 posts / 0 new
Log in or register to post comments
Last post
May 21, 2017 - 3:25pm
#1
silwal
Offline
Last seen: 6 years 11 months ago
Joined: 2017-03-22 05:24
Platform ignores .manifest files

I am trying to use user-defined manifest files with a couple of Portable Apps, but I don't get them to work.

The setup:
I use a computer with HDPi screen, Windows 10, scaling set to 200%. Most of my programs are aware of the high resolution and the Windows setting and scale correctly. Some programs don't (icons and text are tiny). The usual fix is to place an additional manifest file in the folder where the executable sits, named executable.exe.manifest, example given: https://blog.brankovucinec.com/2016/03/19/fix-remote-desktop-dpi-scaling...

The problem:
This fix doesn't work with Portable Apps started from the Platform Launcher. When I start the program directly from the filesystem (not the Portable.exe but the actual original .exe in the folder App) the manifest file is loaded correctly and the program scales well. Starting the same app from the Platform launcher, the manifest file is ignored and the UI-elements are tiny. I have tested with eclipse Mars (self packaged) and GIMP 2.8.

Since it doesn't work with both of them I suppose, it's a general issue of the platform.

Is there a way to force loading the manifest file?

Any help is appreciated,
sil

Top
May 21, 2017 - 4:18pm
John T. Haller
John T. Haller's picture
Offline
Last seen: 4 hours 10 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Launching EXE

I think Windows won't use a manifest unless you are specifically launching the app the manifest is used with. What happens if you put the GIMP manifest alongside GIMPPortable.exe? If that fails, what if you name it GIMPPortable.exe.manifest?

Sometimes, the impossible can become possible, if you're awesome!

Top
May 22, 2017 - 3:18am
(Reply to #2)
silwal
Offline
Last seen: 6 years 11 months ago
Joined: 2017-03-22 05:24
Neither helps

I have tried all possible combinations of naming the manifest files and placing them in both directories.

In terms of GIMP:
- I created both GIMPPortable.exe.manifest and gimp-2.8.exe.manifest
- I placed gimp... in bin and GIMP... in GIMPPortable
- I placed gimp... in bin and in GIMPPortable as well
- I placed GIMP... in bin and in GIMPPortable as well
- I placed both files in both folders
- I placed them crossover
- I even tried all possible combinations of one and two files in both folders

Regardless of the file names and the folder placements, starting GIMP from the Platform Launcher the manifest file is always ignored.

Do you have any further idea?

Thanks in advance,
sil

Top
May 22, 2017 - 9:46am
(Reply to #3)
Gord Caswell
Gord Caswell's picture
Offline
Last seen: 5 months 5 days ago
DeveloperModerator
Joined: 2008-07-24 18:46
Edit internal manifest?

What if you try editing the internal manifest?

  1. Using XN Resource Editor Portable or Resource Hacker Portable, open X:\PortableApps\GIMPPortable\App\gimp\bin\gimp-2.8.exe
  2. Open the manifest section, listed as either "Manifest" or "XP Theme Manifest"
  3. View the manifest itself, and change the section indicated below from "true" to "false"
    <asmv3:application>
		<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
			<dpiAware>true</dpiAware>
		</asmv3:windowsSettings>
	</asmv3:application>
  4. Save the file, and see if this solves your error

Note that this would be a temporary fix, and, just like adding a manifest file, would need to be done until the problem is solved by the application's developers themselves. In the case of GIMP, the developers are aware of the concern.

Top
May 22, 2017 - 1:07pm
silwal
Offline
Last seen: 6 years 11 months ago
Joined: 2017-03-22 05:24
Not solved

Edit: I was too euphoric. It only works if I start from the filesystem (just as with the usual user-compiled manifest). If started from the Launcher, it doesn't work. Sorry for the confusion.

Any more suggestions?

My original reply (before I tested from the Launcher):


Gord's advise (almost) did the trick. I had to replace the original 

<dpiAware>false</dpiAware>

by:

<ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
  false
</ms_windowsSettings:dpiAware>

Thanks a lot!!!

sil

Top
May 22, 2017 - 1:02pm
John T. Haller
John T. Haller's picture
Offline
Last seen: 4 hours 10 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
GIMP folks

Did either of you happen to get in touch with the GIMP folks regarding this? Gord mentioned they were aware of the issue. Perhaps they're waiting because certain features break at this high DPI. I know in our case for the PA.c Platform's menu, it currently messes things up which is why I'm reworking the theme engine to be high DPI aware.

Sometimes, the impossible can become possible, if you're awesome!

Top
May 22, 2017 - 1:13pm
(Reply to #6)
silwal
Offline
Last seen: 6 years 11 months ago
Joined: 2017-03-22 05:24
I have searched many web

I have searched many web sources regarding this. All they currently state is, that one should switch to another theme (which is painful and only helps partly). Rumors are that GIMP 2.9 solves the issue, but it's currently not available for Windows. Note, that Gord's suggestion also didn't help, I was too euphoric with my first reply.

Top
May 22, 2017 - 2:40pm
(Reply to #7)
Gord Caswell
Gord Caswell's picture
Offline
Last seen: 5 months 5 days ago
DeveloperModerator
Joined: 2008-07-24 18:46
No, bugs opened

Icons don't scale well, but are being reworked.

I have not contacted the GIMP folks myself, however I note there are two bugs open - one for the current release stream, and one for the eventual GTK3-based stream.

https://bugzilla.gnome.org/show_bug.cgi?id=725263
https://bugzilla.gnome.org/show_bug.cgi?id=725464

For the current release, the relevant bug states that the manifest needs to be changed.

Top
Log in or register to post comments