HiDPI support

[mstrap]

Please provide support for HiDPI monitors. Currently, the icons are tiny which makes clicking e.g. toolbar buttons hard and in general makes AS look somewhat strange. A simple fix should be to just set dpiAware to false:

https://msdn.microsoft.com/en-us/librar ... 85%29.aspx

Of course it would be great to have AS coming with a separate high-resolution icon set, too

-Marc

[Jan Rysavy]

We are working on it, including new vector icons.

[imkilroy]

Hi, is there a rough timeline for this feature? Thanks

[Jan Rysavy]

It is not finished yet, we have no time estimation right now.

[crystalidea]

Please do it, at least icons adjust size for toolbar and panel items

[Brett]

As an interim measure you can create an external manifest for Salamander that specifies dpiAware as False. That, along with a registry setting that specifies external manifests take preference over internal manifests, has saved my eyesight on a high DPI monitor.

Cheers,
Brett

[prochan2]

Hi, my solution is to right-click the shortcut, go to Properties window, Compatibility tab and select "System" under "Override high DPI scaling behavior." "System (Enhanced)" looks much better, but it brokes UI of TortoiseGit when used from within Salamander.

[camper]

I'm using AS 3.0.8 on a 4k-monitor with 200% scaling and don't have major problems with that, so for me it has no high priority.

[Georgd]

Hi, my solution is to right-click the shortcut, go to Properties window, Compatibility tab and select "System" under "Override high DPI scaling behavior." "System (Enhanced)" looks much better

Thank you for the hint, it's also better on my Huawei MateBook detachable, but icons etc are still quite small for touch operation.

BTW, related posts are Tiny Toolbar Icons on Surface3 screen and Icon size not DPI-aware

[teutonic]

This, for me, is a major deal breaker. Have been a customer for many years and would happily pay for a new, DPI aware version. But sick of waiting. So moving on to Directory Opus. Bye Altap Salamander.

[Georgd]

Dear all, after reading the good news, I just installed Salamander 4.0 on my Win10 PC and was curious for the new High DPI support. And found it's looking blurry while old 3.08 is crisp & clear

2019-07-06 comparision Salamander 3.08 and 4.0.png (230.98 KiB) Viewed 265 times

Only after editing the properties of the .lnk shortcut file, more precisely setting (literally translated from German) compatibility > changing high DPI settings > overwrite high DPI scaling to "System" I got a crisp display. So the same manual configuration step is required as in v3.08, while I expected v4.0 does automatically look good on Win10 & HighDPI. I'm a little sad that High DPI support seems to have been improved only in respect of new icons in SVG - or did I overlook something?

Thank you for hints, Georg

[Jan Rysavy]

Can anyone else reproduce this problem? On our systems AS 4.0 works as expected - all text are crisp and clear (150%, 175%, and 200% scale in Display settings). We didn't change anything in Salamander shortcut properties.

sal_40.png (112.34 KiB) Viewed 249 times

[zarevak]

Dear all, after reading the good news, I just installed Salamander 4.0 on my Win10 PC and was curious for the new High DPI support. And found it's looking blurry while old 3.08 is crisp & clear

How many monitors do you have? Do you have Salamander running on the main monitor? What DPI settings do you have for the different monitors?

Because Salamander doesn't support real-time DPI changes (perMonitor and perMonitor2 HighDPI support), it loads one DPI setting at its startup and stays with it... If it loads DPI setting for the wrong monitor (this is decided by Windows and NOT by Salamander) it becomes blurry, because Windows will do bitmap scalling to the DPI setting of the current monitor.

Only after editing the properties of the .lnk shortcut file, more precisely setting (literally translated from German) compatibility > changing high DPI settings > overwrite high DPI scaling to "System" I got a crisp display. So the same manual configuration step is required as in v3.08, while I expected v4.0 does automatically look good on Win10 & HighDPI. I'm a little sad that High DPI support seems to have been improved only in respect of new icons in SVG - or did I overlook something?

Here is my compatibility settings for Altap Salamander 4.0 which works correctly on my multimonitor system with different DPI settings on different monitors:

(By the way, the Windows Explorer file properties dialog and this compatibility dialog doesn't support perMonitor either on Win 10 1809 - on the second monitor with different DPI it is blurry)