XYplorer Beta Club

Hi
Not sure it qualifies as a bug but quite often on Name Collision the Custom Copy dialog doesn't come to the foreground.
Unfortunately I'm unable to pinpoint the conditions for it to happen (usually, when trying to trigger the problem, all works fine )
Regards

I noted that Windows sometimes keeps windows from coming to the foreground while the CTRL key is held down. Impossible to find any documentation on this.

After reading your answer, I gave it another try:
folder open in windows explorer, 3 files I drag and drop (no ctrl, nothing) to a background XY folder already containing the 3 files » the dialog comes behind the windows explorer window and sometimes the windows behind ! Looks like the dialog may be appearing on the same "plane".
Same experiment several times selecting the different windows on my desktop trying to find a pattern, same result...
This time part of it was visible and it was a test so ok, but sometimes they're completely hidden

What do you mean by "background XY folder"?

I mean XY isn't in the foreground (see bottom right corner of the snapshot).
The way I see it, on drop, if collision, either the XY window should move to the foreground (and the dialog would follow) or the dialog should be brought to the foreground alone). Either way the dialog should be in the foreground else it's possible it's completely invsible.

That's what I figured, and I tested it, and it works as you say it should: XY comes in the foreground. No problems here.

It doesn't happen every time so it's not easy to catch... Too bad.
I'll give an update if I can narrow the conditions. Thanks for looking at it

Does it make a difference when you change this setting:

Configuration | File Operations | File Operations | Miscellaneous | File operation progress dialog modeless

Unfortunately not (usually and currently checked)
And once yesterday, the XY main windows was visible (maybe not in the foreground) and the dialog was hidden.

I added something. Check out the next beta...

Seems to be working better now, at least I'm not wondering any more what's going on !
Thanks for fixing it.