https://bugs.winehq.org/show_bug.cgi?id=51772
Damjan Jovanovic damjan.jov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source URL| |https://github.com/TT-ReBOR | |N/Georgia-ReBORN CC| |damjan.jov@gmail.com
--- Comment #1 from Damjan Jovanovic damjan.jov@gmail.com --- I developed a lot of the drag and drop code, but am unable to test at the moment.
From the log you posted on that forum, it appears to be an interprocess drag
and drop (drag source is in one application, drop target in another), which is why it goes through [drag source] -> XDND -> [drop target's winex11.drv].
Multiple things could be wrong, we don't support IDropTargetHelper::DragOver() or IDataObject::SetData(), the ominous
00f4:fixme:xdnd:X11DRV_XDND_DROPEFFECTToXdndAction unknown drop effect 0, assuming XdndActionCopy
suggests something is also wrong coming in from the drag source, and the drop effect might also not be set correctly in ole32.
It would help a lot to read the source code of the drag source. What is the architecture of your drag source application? It appears to use Python and Javascript somehow. Where is the C/C++ code that calls DoDragDrop()?