Drop indicator not displaying with QTreeView. Need help

[bigchiller]

You can reimplement them, but the default implementation is fine in most cases (and it's responsible for showing the drop indicator). The only reason for reimplementing them I know is when you want to decide if a drop on a particular item should be accepted depending on the contents of a particular drag.

Currently our dragMoveEvent is making the decision whether to use a Qt:CopyEvent or a Qt:MoveEvent. We support either internal moves or dragging external files and copying them into the tree view. Is there a preferred location to place this logic?

[wysota]

The action to be performed could be decided within QAbstractItemModel::dropMimeData(). Of course you can do that in the dropMoveEvent() method, but remember to call the base class implementation.

[bigchiller]

The action to be performed could be decided within QAbstractItemModel::dropMimeData(). Of course you can do that in the dropMoveEvent() method, but remember to call the base class implementation.

dropMoveEvent? Do you mean dragMoveEvent? How would I go about calling the base class implementation if i override dragMoveEvent?

[jpn]

void SubClass::someMethod()
{
    BaseClass::someMethod(); // <---
    // do something in addition to what base class does
    ...
}

void SubClass::someMethod()
{
    BaseClass::someMethod(); // <---
    // do something in addition to what base class does
    ...
}

To copy to clipboard, switch view to plain text mode 

[akiross]

The action to be performed could be decided within QAbstractItemModel::dropMimeData(). Of course you can do that in the dropMoveEvent() method, but remember to call the base class implementation.

My model (subclass of abstract table model) should accept copy actions when dragging from another widget, while accepting move actions when dragging within the widget.

If the action to perform can be decided within QAbstractItemModel::dropMimeData(), how can I operate on the source model when moving?
In other word: if I choose to copy or move within dropMimeData, shoudn't I have access to a QModelIndex for the source data?
I'm wondering:
dropMimeData knows which action should be performed, but returns a bool. So, another object should get this return value and - i guess - this object should check if the move action returned a true and, if it is true, the source object should then ask to source model to remove the data.
How can this be done within dropMimeData?

(Actually I'm really noob with drag and drops, still learning what's behind the curtains

Shouldn't this decision be taken by the view? (e.g. in the startDrag() ?)

Thanks