XYplorer Beta Club

If it is only an issue by drag and drop then you need to set this tweak, BJAllowDropFromOutside=1 and it should resolve it I think, I haven't tested though.

Doesn't work, jupe, tested it with v19.
Are you sure that this should influence a drop from inside XY to the "outside" world (the Desktop GUI)?

No I don't think it should, but you said this

not when you drag and drop to the Desktop link in XYs tree.

which made me think you were talking about to XY not from, and the OP hasn't as yet clearly answered any questions put to them.

which made me think you were talking about to XY not from

No, that was a same instance drag and drop from the network drive in one tab to the Desktop link in the tree

jupe, BJAllowDropFromOutside only affects from outside, not to outside.

Generally, the drop target is responsible for the action, so when you drop to Desktop then Windows does the job. Drag and drop blocks (or can block) the source. I will try to find a way around this...

vrtarifaachen, I need answers:
viewtopic.php?p=180404#p180404

No. As I said above, I checked freezes and problem exists since v17. I didn't check earlier but I think it's been around for a while?

1) Please describe exactly which command you are using to initiate the copy operation.
>>>>>> You can either drag & drop - or use control+C and control+V onto the desktop

2) And it does not matter whether you are using Custom Copy or not, right?
>>>>>>Just to be clear on my language - the setting is ON, but it uses Windows copying when I copy from D > Desktop or Network map drive > desktop I never seen the Custom Copy dialogue box come up when copying to desktop.

3) Does it also happen with Background Processing enabled?
>>>>>>>> Yes

4) What do you mean by "inside" in

When I copy from dir1 > dir2 *inside* XYplorer (using Custom copy) it works perfectly with no desktop freezing.

>>>>>When copying a huge video (e.g. 6GB) from C > D The custom copy window triggers and there is no desktop freezing. It only happens when copying to the desktop when files are copied to windows desktop from XYplorer. This doesn't happen if you completely bypass XYplorer and copy from Windows explorer > Desktop (it only freezes when copying from XYplorer > Desktop)

Thanks.

1) I tested Ctrl+C / Ctrl+V onto the desktop and found no difference whether it's done from XYplorer or from Explorer.
- In both cases Explorer could not be started
- XYplorer was not frozen when doing it from XYplorer.

So what you see (Explorer could not be started) is a Windows problem. Explorer handles the job and won't spawn another thread. Which is strange. (Windows 8.1)

2) Now when doing drag and drop, things are different:
2a) The source (XYplorer) is blocked as long as the copy operation is ongoing.
2b) However, when Explorer is the source, it is not blocked.
2c) When you close Explorer, however, you cannot open it anymore while the copy operation is ongoing.

So, 2b is the interesting case IMO. How can it be it's not blocked?

Please try to change this setting. Does it make a difference?
Configuration | Other | Shell Integration | Drag and Drop | Use standard shell drag and drop

Configuration | Other | Shell Integration | Drag and Drop | Use standard shell drag and drop

It doesn't matter if it's on or off

Ok. I don't see anything I could do. It's all in the hand of Windows.

I see this issue all the time, and it's definitely not just to Desktop as a target. Here is a very reliable way I can reproduce every time:

Select a few large files and drag them into Adobe Audition. While Audition is loading the files, clicking anywhere in XY causes this.

Edit: Also just reproduced in Audacity. I suspect anything that's operating on a large file selection from XY will cause this.

Makes sense. Still cannot do anything about it.

I just bought new faster ssd copy pasting my huge file folder of content to it taking 6 hours the whole Xyplorer just freezes the entire 6 hours now, this behavior wasn't there with explorer I could still use my files and folders while copy pasting stuff...

This would have been your friend:
Configuration | File Operations | File Operations | Background Processing | Enable background processing

Also, if you check this...
Configuration | General | Startup & Exit | Allow multiple instances
... you can always start a new instance if the first instance is busy.