I'm currently updating one app that has 2 executable files.
I already seen the docs but cloud find more details info about the appicon file naming and cardinality.
In the docs we have:
[Control]
Icons=2
Start=AppNamePortable.exe
Start1=AppNamePortable.exe
Name1=AppName Portable
Start2=AppNamePortable2.exe
Name2=AppName Portable Other Part
So I assume we need at least 6 files (appicon.ico, appicon_16.png, appicon_32.png, appicon2.ico, appicon2_16.png, appicon2_32.png). But in this case the executable from Name1 will not have an icon on the PortableApp menu.
I could only put it working properly with duplicated files for executable on Name1 (appicon.ico and appicon1.ico) and so with 9 files (appicon.ico, appicon_16.png, appicon_32.png, appicon1.ico, appicon1_16.png, appicon1_32.png, appicon2.ico, appicon2_16.png, appicon2_32.png).
Is this supposed to happen? Or did I found a little bug?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Yep, it might seem a bit clunky, but that's the way it is supposed to be and is also the way it is documented.
This is by design. When in multi-icon mode, appicon.ico is not used by the platform. appicon1 and appicon2 are used for the 1st two entries. appicon.ico and related are only used by the installer as the app's overall icon when in multi-icon mode.
Note that we generally frown upon multiple icons these days unless genuinely needed. If a 2nd icon is used to run the app in another mode that is accessible within the app during its normal mode, we skip it.
Sometimes, the impossible can become possible, if you're awesome!
Ok, it's documented
Ya, but it's for a different executable.
I assumed appicon.ico would not be used when using appicon1.ico and appicon2.ico, but it is.
So, not problem then
Cheers,
Sam