Revisiting Auto-Scaling

Things you’d like to miss in the future...
Forum rules
:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:

:info: Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: We recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once.

:info: When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".

:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:
ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Revisiting Auto-Scaling

Post by ColdNose »

Hi,

I've searched all the posts I could find on this topic:
viewtopic.php?f=5&t=21264
viewtopic.php?p=175136#p175136, and I believe the latest attempt:
viewtopic.php?f=2&t=21142&hilit=NoAutoScaling&start=30

But they don't address my scaling problem. I have 3 monitors: a primary (new Lenovo X1 notebook) screen: 1920x1080, and 2 identical, higher resolution external screens (3840x1030). I've posted the output from "screen;" and "various information" below.

I've also tried every combination of "NoAutoScaling" tweak and "Override high dpi scaling behavior", etc. possible, and have spent hours rebooting and refreshing ("fresh;") each configuration, etc. to ensure each one is active. In most cases, the changes don't have any significant impact on the problem. This is especially true for the NoAutoScaling tweak which doesn't seem to affect anything.

So, regardless of the myriad of possible settings, I seem to only have two basic unappealing options:

1. With "Override high dpi scaling" turned off, XYPlorer looks great on my Primary (notebook) (1920x1080) screen but doesn't scale when moved to my external monitors and everything appears tiny (font, menu, icons, etc.). Clear, but tiny. In this scenario I can play with font & toolbar sizes, etc. on the external screens, but of course, everything then appears too large when moved back to my primary screen.

2. With "Override high dpi scaling" turned on (set to "System Enhanced" is best), everything scales properly as I move from screen to screen. However, now the problem is that all text, icons, etc. appears fuzzy when using the primary screen (however, the external screens are clear).

Thoughts? Suggestions? The first option above is the best if only XYPlorer will scale when moved to a higher resolution screen.

I was hoping this might be resolved with the 64bit conversion but that's now off the table. In the last post above, the admin suggested that the problem is "on his list". Any progress - or chance to revisit this problem?

Thanks!!

Output from "screen;" on the primary monitor with "NoAutoScaling=0" and "Override high dpi scaling" turned off:
Screen

Code: Select all

XYplorer 21.20.0200  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 1920 (1920)
Screen.Height (screenH) = 1080 (1080)
Current Monitor: 1 (Primary)
Current Work Area: (0, 0) - (1920, 1030)

Number of Monitors: 3
Monitor 1 Area:      (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 2 Area:      (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 3 Area:      (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 516, 96
XY Main Window: (-9, -9) - (1929, 1039) = 1938x1048

Screen DPI: 120 (125%)   twx: 12 (12)   stretch: 1   sLF: 1.25
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes
Output from Various Information:

Code: Select all

XYplorer: 21.20.0200 (Pro Edition - Lifetime License Pro)
Loaded in: 974 ms at 11/24/2020 9:27:47 AM
Uptime: 48 mins, 51 secs    Runtime: 6.00.9815
Memory Usage: 43,408 KB, Virtual Memory Size: 20,080 KB

OS: Windows 10 Professional, 64-bit, Release 2004, Build 19041.630
OS Uptime: 55 mins, 39 secs
Time Zone: SE Asia Standard Time, SE Asia Daylight Time
UTC Offset: +07:00
User Role: User
Themes: Yes (Aero)    RealSystem32: Yes

System Locale ID: 1033 (en-US)
Thread Locale ID: 1033 (en-US)
Default ANSI Code Page: 1252  (ANSI - Latin I)
Active ANSI Code Page: 1252  (ANSI - Latin I)
Default OEM code page: 437   (OEM - United States)
Active OEM Code Page: 437   (OEM - United States)
DBCS Code Page: No
Main Contents Font: Segoe UI 9

DblClick Time: 500 ms
Screen: 1920x1080, 1/3 (Primary), Virtual: (-2875, -2160) - (7680, 3240), Work: (0, 0) - (1920, 1030)
Screen DPI: 120 (125%), twx: 12, stretch: 1
Screen Color Depth: 32
DPI awareness: Per monitor
UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

XYplorer should scale when moved to a higher resolution screen. At least I told it to do so. :veryconfused: Are you sure that NoAutoScaling is set to 0?

ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Re: Revisiting Auto-Scaling

Post by ColdNose »

Thanks for the reply.

Yes, confirmed "NoAutoScaling=0". The same situation happens with "fresh;" and I saved a copy of the current config file and verified the NoAutoScaling=0 tweak was set.

Setting it "NoAutoScaling=1" and restarting without saving (and making a copy of the config file to verify!) makes no difference. It still displays perfect on my primary screen, but tiny on my higher resolution screen. So, I don't think the scaling is working either way.

Is there any way to check that scaling was tried?

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

When you run screen; through the address bar, you should see this line in the return if auto-scaling is enabled (generally, and for the toolbar):

Code: Select all

Auto Scaling: Yes, Yes
In the next beta I will add three events to the debug log:

Code: Select all

WM_SETTINGCHANGE (SPI_SETWORKAREA):
WM_DISPLAYCHANGE: 
WM_DPICHANGED: 
After you moved XY to a another monitor you should see either of them in the debug log when you run dlog; through the address bar.

ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Re: Revisiting Auto-Scaling

Post by ColdNose »

Thanks for looking into this.

I've installed the beta 21.30.0005. I then moved XY from my Primary to external monitor and received this with "dlog;" :

Code: Select all

Debug Log  XYplorer 21.30.0005  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-01 08:50:42.891
----------------------------------------------------------------------------------------------------

           -  2020-12-01 08:50:35.235  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
I also receive this with the "screen;" command:

Code: Select all

Screen
XYplorer 21.30.0005  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 1920 (1920)
Screen.Height (screenH) = 1080 (1080)
Current Monitor: 3 (Secondary)
Current Work Area: (965, -2160) - (4805, -80)

Number of Monitors: 3
Monitor 1 Area:      (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 2 Area:      (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 3 Area:      (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 1190, -1951
XY Main Window: (956, -2169) - (4814, -71) = 3858x2098

Screen DPI: 120 (125%)   twX: 12 (12)   Stretch: 1   sLF: 1.25   Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40
Moving XY from the extended screen to my primary screen, gives me this with "dlog;" :

Code: Select all

Debug Log
XYplorer 21.30.0005  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-01 08:57:24.181
----------------------------------------------------------------------------------------------------

           -  2020-12-01 08:50:35.235  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
 6:42.405  -  2020-12-01 08:57:17.640  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
And "screen;" on my Primary monitor shows this:

Code: Select all

Screen
XYplorer 21.30.0005  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 1920 (1920)
Screen.Height (screenH) = 1080 (1080)
Current Monitor: 1 (Primary)
Current Work Area: (0, 0) - (1920, 1030)

Number of Monitors: 3
Monitor 1 Area:      (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 2 Area:      (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 3 Area:      (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 0, 100
XY Main Window: (-9, -9) - (1929, 1039) = 1938x1048

Screen DPI: 120 (125%)   twX: 12 (12)   Stretch: 1   sLF: 1.25   Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40
Any thoughts? It looks like it is trying to autoscale... but just doesn't scale large enough!

Thanks, once again.

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

Interesting. The screen command shows "Screen DPI: 120 (125%)" on both monitors, which is of course wrong!

This is good. Not sure yet how to fix it but I smell the blood. There will be a solution... :cup:

ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Re: Revisiting Auto-Scaling

Post by ColdNose »

If it helps, my scale settings for my secondary monitors is 200%. I've played around with this on each monitor and confirmed that other windows apps (.ie, File Explorer) work as expected: scaling to the setting of each monitor. However, XY's screen; continues to report the screen DPI of the primary monitor ("120 (125%)") for each secondary monitor regardless of its scale setting.

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

With a bit of luck v21.30.0017 might fix the issue. Please try...

ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Re: Revisiting Auto-Scaling

Post by ColdNose »

Unfortunately, no joy. We've gone backwards. The toolbar, tab and breadcrumb lines are now only displaying half height on both the Primary and Secondary screens (see images below). Scaling still doesn't work on the Secondary screens.

Here's the primary screen:
Primary Screen
Primary Screen
201209_Primary Screenshot.png (91.14 KiB) Viewed 4696 times
And the screen; output for the Primary Screen:

Code: Select all

Screen
XYplorer 21.30.0022  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 3291.42857142857 (1920)
Screen.Height (screenH) = 1851.42857142857 (1080)
Current Monitor: 1 (Primary)
Current Work Area: (0, 0) - (1920, 1030)

Number of Monitors: 3
Monitor 1 Area:      (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 2 Area:      (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 3 Area:      (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 140, 105
XY Main Window: (-9, -9) - (1929, 1039) = 1938x1048

Screen DPI: 0 (0%)   twX: 7 (12)   Stretch: 2   sLF: 2.142857   Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40
Here is the Secondary screen:
201209_Extended Screenshot.png
201209_Extended Screenshot.png (134.19 KiB) Viewed 4696 times
And the screen; output for the Secondary Screen:

Code: Select all

Screen
XYplorer 21.30.0022  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 3291.42857142857 (1920)
Screen.Height (screenH) = 1851.42857142857 (1080)
Current Monitor: 2 (Secondary)
Current Work Area: (-2875, -2160) - (965, -80)

Number of Monitors: 3
Monitor 1 Area:      (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 2 Area:      (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 3 Area:      (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = -2875, -2072
XY Main Window: (-2884, -2169) - (974, -71) = 3858x2098

Screen DPI: 0 (0%)   twX: 7 (12)   Stretch: 2   sLF: 2.142857   Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40
And here's dlog; when moving from Primary to Secondary and back to Primary

Code: Select all

XYplorer 21.30.0022  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-09 09:26:48.475
----------------------------------------------------------------------------------------------------

           -  2020-12-09 09:23:10.689  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
 2:40.075  -  2020-12-09 09:25:50.764  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
   53.383  -  2020-12-09 09:26:44.147  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

Sorry, I made a mistake in the implementation. Please try the next beta v21.30.0023.

ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Re: Revisiting Auto-Scaling

Post by ColdNose »

Sorry, but it looks the same. No visual change from 21.30.0022

However, I see that the "Screen DPI" line has changed in the screen; command for both the primary and secondary:

Primary Screen;

Code: Select all

Screen
XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 1920 (1920)
Screen.Height (screenH) = 1080 (1080)
Current Monitor: 1 (Primary)
Current Work Area: (0, 0) - (1920, 1030)

Number of Monitors: 3
Monitor 1 Area: (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 1 DPI: 120 (125%)
Monitor 2 Area: (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 2 DPI: 192 (200%)
Monitor 3 Area: (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)
Monitor 3 DPI: 192 (200%)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 182, 104
XY Main Window: (-9, -9) - (1929, 1039) = 1938x1048

Screen DPI: 120 (125%)   twX: 12 (12)   Stretch: 1   sLF: 1.25   Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40
Secondary Screen;

Code: Select all

Screen
XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630

Virtual Screen: (-2875, -2160) - (7680, 3240)

Screen.Width (screenW) = 3291.42857142857 (1920)
Screen.Height (screenH) = 1851.42857142857 (1080)
Current Monitor: 3 (Secondary)
Current Work Area: (965, -2160) - (4805, -80)

Number of Monitors: 3
Monitor 1 Area: (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 1 DPI: 120 (125%)
Monitor 2 Area: (-2875, -2160) - (965, 0) = 3840x2160
Monitor 2 Area Work: (-2875, -2160) - (965, -80)
Monitor 2 DPI: 192 (200%)
Monitor 3 Area: (965, -2160) - (4805, 0) = 3840x2160
Monitor 3 Area Work: (965, -2160) - (4805, -80)
Monitor 3 DPI: 192 (200%)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 1715, -875
XY Main Window: (956, -2169) - (4814, -71) = 3858x2098

Screen DPI: 192 (200%)   twX: 7 (12)   Stretch: 2   sLF: 2.142857   Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40

Here's the primary screen:
201210_Primary Screenshot.png
201210_Primary Screenshot.png (95.06 KiB) Viewed 4668 times
Here's the dlog; after moving from screen to screen

Code: Select all

XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-10 06:12:15.368
----------------------------------------------------------------------------------------------------

           -  2020-12-10 06:10:02.129  ---  DPI for monitor 2: 192, 192
   12.574  -  2020-12-10 06:10:14.703  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-10 06:10:14.703  ---  DPI for monitor 3: 192, 192
   13.456  -  2020-12-10 06:10:28.159  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
           -  2020-12-10 06:10:28.159  ---  DPI for monitor 1: 120, 120
    1.250  -  2020-12-10 06:10:29.409  ---  WM_DPICHANGED: 12583104, 1703284, dpiX=192, dpiY=192
           -  2020-12-10 06:10:29.409  ---  DPI for monitor 2: 192, 192
    1.088  -  2020-12-10 06:10:30.497  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
           -  2020-12-10 06:10:30.497  ---  DPI for monitor 1: 120, 120
      728  -  2020-12-10 06:10:31.225  ---  WM_DPICHANGED: 12583104, 1703284, dpiX=192, dpiY=192
           -  2020-12-10 06:10:31.225  ---  DPI for monitor 2: 192, 192
    2.247  -  2020-12-10 06:10:33.472  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
           -  2020-12-10 06:10:33.472  ---  DPI for monitor 1: 120, 120
 1:33.170  -  2020-12-10 06:12:06.642  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-10 06:12:06.642  ---  DPI for monitor 3: 192, 192

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

ColdNose wrote: 10 Dec 2020 00:18 Here's the dlog; after moving from screen to screen

Code: Select all

XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-10 06:12:15.368
----------------------------------------------------------------------------------------------------

           -  2020-12-10 06:10:02.129  ---  DPI for monitor 2: 192, 192
   12.574  -  2020-12-10 06:10:14.703  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-10 06:10:14.703  ---  DPI for monitor 3: 192, 192
   13.456  -  2020-12-10 06:10:28.159  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
           -  2020-12-10 06:10:28.159  ---  DPI for monitor 1: 120, 120
    1.250  -  2020-12-10 06:10:29.409  ---  WM_DPICHANGED: 12583104, 1703284, dpiX=192, dpiY=192
           -  2020-12-10 06:10:29.409  ---  DPI for monitor 2: 192, 192
    1.088  -  2020-12-10 06:10:30.497  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
           -  2020-12-10 06:10:30.497  ---  DPI for monitor 1: 120, 120
      728  -  2020-12-10 06:10:31.225  ---  WM_DPICHANGED: 12583104, 1703284, dpiX=192, dpiY=192
           -  2020-12-10 06:10:31.225  ---  DPI for monitor 2: 192, 192
    2.247  -  2020-12-10 06:10:33.472  ---  WM_DPICHANGED: 7864440, 1703284, dpiX=120, dpiY=120
           -  2020-12-10 06:10:33.472  ---  DPI for monitor 1: 120, 120
 1:33.170  -  2020-12-10 06:12:06.642  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-10 06:12:06.642  ---  DPI for monitor 3: 192, 192
The screen; looks perfect.

But concerning that dlog;, on which monitor did you start up?

ColdNose
Posts: 36
Joined: 16 Jun 2017 09:21
Location: Win11, 3 monitors: (1) 1920x1200 @ 125%, (2) 3840x2160 @ 175%

Re: Revisiting Auto-Scaling

Post by ColdNose »

You should've been a detective! ha!

dlog; indeed reveals the problem. I did 4 tests with each test starting on a different monitor and moving in different pattern among the monitors. See the results below:

Here's what I found:
a) regardless of which monitor I start XY on, dlog always shows that I started on monitor 2 [192, 192];
b) moving between monitors 2->3 or 3->2 (secondary screens) does not register in dlog (the change is not shown);
c) moving from a secondary monitor to the primary monitor (or vice versa) always show correctly.

Interestingly, if I move from primary monitor to a secondary, the tabs and breadcrumbs rows show full height, however the toolbar remains half height. Moving from secondary to primary, the tabs and breadcrumb rows reduce back down to half height. Moves between secondary monitors (2->3, 3->2) do not affect the row heights. This is consistent with changes shown in dlog;.

Test Results and Steps Taken:

Code: Select all

TEST 1 =================================================================================================================
Steps:
1) Start on monitor 1 (Primary)
2) Move to monitor 3 (dlog shows change)
3) Move to monitor 1 (dlog shows change)
4) Move to monitor 3 (dlog shows change)
5) Move to monitor 1 (dlog shows change)

Debug Log
XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:24:58.406

XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:24:58.406
----------------------------------------------------------------------------------------------------

           -  2020-12-11 08:22:26.107  ---  DPI for monitor 2: 192, 192
 1:14.675  -  2020-12-11 08:23:40.782  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-11 08:23:40.782  ---  DPI for monitor 3: 192, 192
   18.424  -  2020-12-11 08:23:59.206  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
           -  2020-12-11 08:23:59.206  ---  DPI for monitor 1: 120, 120
   31.511  -  2020-12-11 08:24:30.717  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-11 08:24:30.717  ---  DPI for monitor 3: 192, 192
   23.722  -  2020-12-11 08:24:54.439  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
           -  2020-12-11 08:24:54.440  ---  DPI for monitor 1: 120, 120
		   
TEST 2 =================================================================================================================
Steps:
1) Start on monitor 2
2) Move to monitor 3 (dlog doesn't show change)
3) Move to monitor 1 (dlog shows change)
4) Move to monitor 2 (dlog shows change)
5) Move to monitor 3 (dlog doesn't show change
6) Move to monitor 1 (dlog shows change)


Debug Log
XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:29:38.892

XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:29:38.892
----------------------------------------------------------------------------------------------------

           -  2020-12-11 08:28:06.254  ---  DPI for monitor 2: 192, 192
   31.383  -  2020-12-11 08:28:37.637  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
           -  2020-12-11 08:28:37.637  ---  DPI for monitor 1: 120, 120
   19.043  -  2020-12-11 08:28:56.680  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-11 08:28:56.680  ---  DPI for monitor 2: 192, 192
   38.517  -  2020-12-11 08:29:35.197  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
           -  2020-12-11 08:29:35.197  ---  DPI for monitor 1: 120, 120
		   
TEST 3 =================================================================================================================
Steps:
1) Start on monitor 3
2) Move to monitor 2 (dlog doesn't show change)
3) Move to monitor 1 (dlog shows change)
4) Move to monitor 3 (dlog shows change)
5) Move to monitor 2 (dlog doesn't show change
6) Move to monitor 1 (dlog shows change)

Debug Log
XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:35:51.937

XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:35:51.937
----------------------------------------------------------------------------------------------------

           -  2020-12-11 08:34:27.688  ---  DPI for monitor 2: 192, 192
   30.244  -  2020-12-11 08:34:57.932  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
           -  2020-12-11 08:34:57.932  ---  DPI for monitor 1: 120, 120
   16.459  -  2020-12-11 08:35:14.391  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-11 08:35:14.391  ---  DPI for monitor 3: 192, 192
   33.396  -  2020-12-11 08:35:47.787  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
        1  -  2020-12-11 08:35:47.788  ---  DPI for monitor 1: 120, 120
		
TEST 4 =================================================================================================================
Steps:
1) Start on monitor 1
2) Move to monitor 2 (dlog shows change)
3) Move to monitor 1 (dlog shows change)
4) Move to monitor 3 (dlog shows change)
5) Move to monitor 2 (dlog doesn't show change

Debug Log
XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:38:09.360

XYplorer 21.30.0026  -  Windows 10 Professional, 64-bit, Release 2004, Build 19041.630  -  2020-12-11 08:38:09.360
----------------------------------------------------------------------------------------------------

           -  2020-12-11 08:37:19.353  ---  DPI for monitor 2: 192, 192
    6.729  -  2020-12-11 08:37:26.082  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-11 08:37:26.082  ---  DPI for monitor 2: 192, 192
   14.779  -  2020-12-11 08:37:40.861  ---  WM_DPICHANGED: 7864440, 1699348, dpiX=120, dpiY=120
           -  2020-12-11 08:37:40.861  ---  DPI for monitor 1: 120, 120
    8.261  -  2020-12-11 08:37:49.122  ---  WM_DPICHANGED: 12583104, 1699348, dpiX=192, dpiY=192
           -  2020-12-11 08:37:49.122  ---  DPI for monitor 3: 192, 192

admin
Site Admin
Posts: 65043
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: Revisiting Auto-Scaling

Post by admin »

Thanks for your report, and sorry to come back so late! I was busy with the same problem. :) In the meantime I removed much of the code that fruitlessly attempted to auto-scale the app. I'm still investigating the options that remain, but not as my primary activity anymore.

So, I guess with latest betas (v21.30.0037 on) your findings will be outdated, unfortunately. You certainly should not see those half-bars anymore.

moguiyu
Posts: 9
Joined: 08 Oct 2018 14:38

Re: Revisiting Auto-Scaling

Post by moguiyu »

was waiting for the fix for auto-scaling for years, hope it will finally supported soon.
the latest verison 21.50.0100 still does not auto-scale to different monitor.

Post Reply