XY window not opening to saved position

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 strongly 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, and we won't have to search for that vital information.

: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:
Post Reply
jupe
Posts: 3462
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

XY window not opening to saved position

Post by jupe »

Something that has been niggling me for a while now, is that I have always had XY aero snapped to the LHS of my screen in my normal config, but now when XY loads it is horiz inset what visually looks like ~3 pixels instead, although it is actually at 0,0 according to screen; My conf is still set WinX=-8 same as always, anyway I finally decide to narrow down the version the issue started and I have got it to this change:

Code: Select all

v24.60.0102 - 2023-07-16 12:14
    % Startup: Now it is ensured that the upper left corner of the main window is visible 
      and that at least 256 pixels in width and height are visible, no matter which 
      monitor in your multi-monitor setup has been turned off since the last session.
Is there a possibility to redesign this check, so that I can still launch XY with an aero snapped value?, Y can be 0, but for me aero snap produces -8 for X. And if maximized it is -9,-9, but I don't save my config like that, so am not personally affected. I don't have a multi monitor setup.

Code: Select all

Virtual Screen: (0, 0) - (1920, 1080)

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

Number of Monitors: 1
Monitor 1 Area: (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 1 DPI: 120 (125%)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 1059, 231
XY Main Window: (-8, 0) - (968, 1038) = 976x1038, Scale: 958x966

Monitor: 1/1 (Primary)
Screen: 1920x1080   Virtual: (0, 0) - (1920, 1080)   Work: (0, 0) - (1920, 1030)
Screen DPI: 120 (125%)   twX: 12 (12)   Stretch: 1.25   sLF: 1.25   Toolbar Zoom: 1.10 (1;1)
Screen Color Depth: 32   Line Spacing: 2 (2.50)
DPI Awareness: Per monitor   Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes
Icon Size: Small=16, Large=32, Extra Large=48, Jumbo=256
Icon Size Controls: Small=20, Large=40, Extra Large=48, Jumbo=256
Icon Size Recommended: Small=20, Large=40, Extra Large=48, Jumbo=256

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

Re: XY window not opening to saved position

Post by admin »

It is 0 but looks like 3 I guess. So if I allowed negative X values down to -8 your issue would be history, right?

highend
Posts: 14991
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: XY window not opening to saved position

Post by highend »

-10 should be save as well

Title bar heights are normally around 30 px so you'd still see 2/3 of to be able to grab and move it
One of my scripts helped you out? Please donate via Paypal

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

Re: XY window not opening to saved position

Post by admin »

You're welcome.

jupe
Posts: 3462
Joined: 20 Oct 2017 21:14
Location: Win10 22H2 120dpi

Re: XY window not opening to saved position

Post by jupe »

I'm too late now, but yes -8 I think would have resolved it for me, but I am not sure how other screen sizes/dpi or OS's were affected in the same scenario, so I also agree -10 was probably a safer choice, and I can confirm it is back to normal now in .0008,

Thanks!

Post Reply