XYplorer Beta Club

XYplorer v20.20.0200 (not yet registered) Windows 10 x64

I cannot drag and drop a file (well, filename, I guess) from XYplorer onto notepad. (Nor onto Notepad++ 64bit which is where I first saw this).

The Shell Integration option to use standard drag and drop is ticked (makes no difference).

The Tools / Customize List / Manual Sorting option is NOT ticked (if ticked the drag drop doesn't even look like working).

When attempting the small "+" symbol appears with the mouse when hovering over the destination, but no icon as appears with successful destinations. For example I can drag the file onto Firefox (v67 64bit) and it loads as expected.

In all cases all processes are running under my normal, non-administrator, user.

The drag and drop works when using Windows File Explorer (or the XYplorer competitor I normally use but was wanting to replace).

I quite often need to drag and drop files this way - in particular files with no file extension because you cannot associated them for double-click loading.

Then either start the 32-bit notepad version (C:\Windows\SysWOW64\notepad.exe)
or create a PFA entry like *.>::run ""notepad.exe"" ""<curitem>"""; (because you can
assign non-extension files to be double clicked via a PFA...)^^

Thanks, that PFA idea (once I looked it up in the help index to find out what it was ;-)) is a useful work around.

Your response (and the fact that 32-bit notepad does actually work here) suggests the problem is a 32-bit over 64-bit issue ... and yet I can successfully drop onto 64-bit Firefox or Vivaldi internet browsers and have the file open (Vivaldi is a bit inconsistent about where it will accept the drop, but does actually work). Is this because those browsers do something extra to allow it (so it's in control of the receiver not the sender) or ... ?

Yes, the receiver is responsible for handling the drop and performing the required action (e.g. file operations). Of course, the sender has to do it right as well. But there are many ways to do it for a sender, and with every version Windows comes up with new rules. So a good receiver should show some tolerance.

To make it worse there is an unfixed bug in Windows that can affect drops from 32-bit to 64-bit.