XYplorer Beta Club

Try v26.20.0200, I added something: Next time XY pops up to the front, type dlog; in its address bar and press ENTER. A debug log will come up and should tell us something interesting.

Thanks for making the effort! I tried, but nothing show up in the log:

XYplorer 26.20.0200 - 30-Day Trial Version - Day 1 - Windows 11 Pro, 64-bit, Version 23H2, Build 22631.2861 (10.0) - 2024-07-12 12:44:06
==============================================================================================================================================

Also, i hooked into windows shell events to look for a clue, all i got was:
1. the application on second desktop exiting with window parameter 2 (HSHELL_WINDOWDESTROYED)
2. xyplorer activating on desktop 1 with window parameter 32772 (HSHELL_RUDEAPPACTIVATED|HSHELL_HIGHBIT)
3. root window of explorer (desktop) activating on desktop 1 with 32772 (HSHELL_RUDEAPPACTIVATED|HSHELL_HIGHBIT)

Honestly, don't waste too much time on this issue for my sake. I'd be happy to help of course, but if noone else has this problem maybe it's a waste of your time.

Hm, the log is empty. That means:

1) No chance to fix it. Windows does it all by itself.

2) Since this is Windows 11, chances are that this is just a Windows bug. (Which means it will never be fixed.)

I agree the case can be closed here.

Not sure if it is related but I have an issue where if I have 2+ instances of XY open (which I always do), regularly if the XY process is delayed (slow lan response etc) they end up swapping order on the taskbar, this is what I get in that situation:
When they swap order on the taskbar I have to close the second instance to return the first back to the first position, it can get irritating. It's happening frequently lately because I've plugged in an old slow NAS.

What you see is the solution to the focus issue mentioned here: viewtopic.php?p=77516#p77516
I'd say it's a workaround for a shell bug. Now it may be that the bug is fixed in Win 10 and later (unlikely, of course), so I will experimentally remove the workaround for Win 10 and later. Let me know how it works.

Been using .0206 for 2 days now, and my issue seems fixed.

It will be great not having that irritation anymore, and I haven't noticed any abnormal behavior in regards to XY being left in the background yet either. I'd be interested to know if this resolves the OPs issue too.

Enormous Thanks!

Great!

Now I'm waiting for the complaints from the other side (the focus loss folks) .