Hello,
Wow I just plugged my PortableApps drive into a laptop with a high-definition screen and it came out looking like this,
The icon is all jagged and crude looking. I assume it's an .ico, correct?
Any chance this can be updated for computers with HD screens?
Thanks
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Hi gwt10, it looks OKish on my 3000x2000 screen. Not crisply brilliant, though.
Well it's pretty bad on mine. It sticks out like a sore thumb.
The built-in icon has versions up to 256px/16.8mil colors. The problem most likely arises when the display scaling is changed as you normally do on high dpi screens. When you look at your wifi icon, you see the exactly the same scaling problems. Windows itself chooses which icon is used for the taskbar and does the scaling, too.
I don't know, if anything can be changed in the way the PortableAppsPlattform.exe is compiled to solve that issue.
You said that in the plural. You mean there are other versions? If so then where can I get them and how do I install it?
I'm also actually hoping the developer is reading this and could address this scaling issue in a later update.
It's in the exe itself (you can check with Resource Hacker if you like).
I doubt, the developer of Windows 10 (Microsoft) is reading this and would adress the scaling issue in a later update. It is a well known problem that Microsoft has not fixed on the last 10 years or so.
On my surface it mostly occurs after powering up from standby or hibernation mode. It affects not all apps but sometimes even the icons pinned to the taskbar. Even the icons of coreldraw, word or edge are jagged sometimes. Working with displays with different resolutions (e.g. using a beamer or so and thus changing resolution forth and back) does itensify this effect.
Rebooting would fix this issue or rebuilding the icon cache by restarting explorer.exe via taskmanager. But I don't care.
I wouldn't expect micro$oft to fix it. I was hoping John Haller or somebody might have a workaround for it in the future.