XYplorer Beta Club

Good question. Since you were the only one to report this issue something might be wrong with Win11 or with your system. However, if that would be the case I should have gotten error reports from other users in the meantime because that fix changes the way it worked before for everybody (with > 1 monitor). Up to now I had no complaints.

I cannot give any programming advice since I never really saw the situation with 2 monitors. All my fixing was in the dark, based on the debug log.

The GitHub dev I was talking to said he implemented multi-monitor support on a Win 10 system, and last he knew, it still worked. So yes, as you said, it's either my system, or a new quirk in Win 11. At this moment, I'm leaning towards it being a Win 11 quirk as I don't have anything running that should interfere or change the behaviour of window placement.

It's a shame that no one else with 2 monitors interfered in the thread to share a second experience.

Hi all.

I have two screens, and have started to notice that the placement of the MDBU (left or right mouse button) positioning, especially for text files, does not persist across XY restart.

Start XY on my primary monitor (no.1), top right. MDBU on an image, image blows up at the cursor. MDBU on a txt file, image appears on the no.2 monitor every time.

Then I accidentally moved the XY window slightly, and on the next MDBU, the text file blow up correctly appeared on the primary. This continued until I closed and restarted XY, when the original behaviour reoccurred, i.e images on the primary over the XY window, text on the no.2 monitor. After a bit more play^H^H^H^H testing, I found that it was not necessary to move the whole window slightly; instead I can move any of the edges of the XY window a fraction, and that suffices to set the positioning correctly. Close and re-start XY, and the original, incorrect, behaviour returns.

Hope this helps track down the issue.

Running Win10 ver 20H2.

Hi, interesting observations! It should be fixed in next beta.

Fix works perfectly on my systems.

Thank-you.

Thank you. Your observations made my mistake obvious: I tested for the current monitor *before* the main window was shown. Does not work that way.