After browsing a bunch (100+) of graphics files and using floating preview (#178) on them, XY's UI becomes corrupted (see example image).
Moving the window around and clicking inside it hints that the UI is still intact but just the display is affected.
Edit: It just happened again. I had been browsing some more graphics files (using #178 via a script), but was actually triggered after using 7-zip to unpack somefiles into a folder. (see new example). I opened a zip file with 7zip and then dragged the contents of the zip a folder. It looks like the "Replace or Skip files" dialogue was displayed.
After killing and restarting XY, the same operation worked fine.
XY64: UI corrupted after using floating preview
Forum rules
When reporting a bug, please include the following information: your XYplorer version (e.g., v27.90.0047), your Windows version (e.g., Win 11), and your screen scaling percentage (e.g., 125%). We recommend adding your Windows version and screen scaling percentage to your profile or signature. This will make debugging much easier for us.
When reporting a bug, please include the following information: your XYplorer version (e.g., v27.90.0047), your Windows version (e.g., Win 11), and your screen scaling percentage (e.g., 125%). We recommend adding your Windows version and screen scaling percentage to your profile or signature. This will make debugging much easier for us.
XY64: UI corrupted after using floating preview
Windows 11 Pro x64
XYplorer 28.80.0007 x64 beta
XYplorer 28.80.0007 x64 beta
-
- Site Admin
- Posts: 64695
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: XY64: UI corrupted after using floating preview
Currently, no bugs are being fixed at TB. Let's wait for the next release, which I hear will bring many improvements, and see how it goes.
FAQ | XY News RSS | XY X
Re: XY64: UI corrupted after using floating preview
Ok. I will keep an eye out. 

Windows 11 Pro x64
XYplorer 28.80.0007 x64 beta
XYplorer 28.80.0007 x64 beta
Re: XY64: UI corrupted after using floating preview
Sadly this issue is still happening for me:

Windows 11 Pro x64
XYplorer 28.80.0007 x64 beta
XYplorer 28.80.0007 x64 beta
-
- Site Admin
- Posts: 64695
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: XY64: UI corrupted after using floating preview
Too early. We are still waiting for the next release.
FAQ | XY News RSS | XY X
Re: XY64: UI corrupted after using floating preview
No worries.
Just didn't want you to forget about me.
Just didn't want you to forget about me.

Windows 11 Pro x64
XYplorer 28.80.0007 x64 beta
XYplorer 28.80.0007 x64 beta
Re: XY64: UI corrupted after using floating preview
I know you are aware of this bug and would just like to add that the garbled graphics do affect the Windows Taskbar as well (I added the orange rectangles for privacy reasons):
Whatever is causing the XYplorer surface to get corrupted, it also corrupts a Windows component or the graphics driver. The Taskbar corruption remains when I close and restart XYplorer (until I force Windows to re-draw the Taskbar). It happens infrequently and can therefore not be replicated.
Whatever is causing the XYplorer surface to get corrupted, it also corrupts a Windows component or the graphics driver. The Taskbar corruption remains when I close and restart XYplorer (until I force Windows to re-draw the Taskbar). It happens infrequently and can therefore not be replicated.
XYplorer x64 (often the latest beta), Windows 10 Pro 22H2, 3840x2160 scaling 100%
-
- Site Admin
- Posts: 64695
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: XY64: UI corrupted after using floating preview
Crass! (Never saw it here though)
FAQ | XY News RSS | XY X
-
- Posts: 55
- Joined: 21 Oct 2012 21:51
- Location: Microsoft Windows Version 241-12 (0S Build 26100.4946) 200% screen scale (recommended)
Re: XY64: UI corrupted after using floating preview
I've seen that with the side window preview with heavy preview activity. After some time the display distorts and locks up. Restart solves it, though inconvenient.