Bug in Qt 5.12 drag n'drop ?

[cawlfj]

@SGaist
i found same bug also in my app. change back 5.11 drop come back.
windows10 qt5.12.0 QLinedit , can drag from QLineEdit , but can't drop to QLineEdit.
Sometimes press the "ctrl" can drop to QLineEdit.

[ModelTech]

I have checked the drag & drop in my app when running on Ubuntu 16.04. The drag is from a QListWidgetItem to a drop on a QGraphicsView. I appropriately overrode QGraphicsView::dropEvent (and all the drag methods of QGraphicsView). It still works in Qt5.12.0 although the willingness to accept the QMimeData constructed from the QListWidgetItem as a droppable on the QGraphicsView (visible as a change in the mouse pointer icon) seems to be less than it was with Qt5.7 that I used up to yesterday. No clue whether this is in any way related, but perhaps it brings some ideas of what causes the issue for dropping on a QLineEdit.

[SGaist]

@ModelTech can you provide a minimal compilable example that shows that change of behaviour ?

[ReDEnergy]

Hi. I had the same problem. Everything worked fine on Qt 5.7 then after I updated to Qt 5.12 dropping would not work at all.
At least in my case it seems that for previous version of Qt only implementing dragEnterEvent was enough but with 5.12 I had to also override the dragMoveEvent event.
So, basically I have this 2 things and now it works as expected. Hope it helps someone.

void QtDropArea::dragEnterEvent(QDragEnterEvent *event)
{
	event->acceptProposedAction();
}

// this was added after updating to Qt 5.12
void QtDropArea::dragMoveEvent(QDragMoveEvent *event)
{
	event->acceptProposedAction();
}

[Christian Ehrlicher]

@ReDEnergy said in Bug in Qt 5.12 drag n'drop ?:

QtDropArea

From what did you derive QtDropArea?

[ReDEnergy]

from the classic QWidget

[Christian Ehrlicher]

Thx for your hint with the dragMoveEvent() reimpl. I think I can reproduce your issue and also found the corresponding commit.

[Christian Ehrlicher]

Can you please check if you get a dragEnterEvent in the problematic case? I would guess no.
The problem was introduced with f8944a7f07112c85dc4f66848cabb490514cd28e which is a bugfix for QTBUG-67155.

[ReDEnergy]

Great to hear that. So, I suppose what I did is a workaround for the moment, but at least it works.

[aha_1980]

@Christian-Ehrlicher I already did some cross-links, can you create a bugreport for that issue?

[Christian Ehrlicher]

https://bugreports.qt.io/browse/QTBUG-72844 and https://codereview.qt-project.org/249086

[Christian Ehrlicher]

The bug will be fixed in 5.12.1