Bug 290869

Summary:	Drag'n'Drop mail to another folder: don't offer position in between folders
Product:	[Applications] kmail2	Reporter:	Bernd Oliver Sünderhauf <pancho.s>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	LO
Version:	4.9.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Bernd Oliver Sünderhauf 2012-01-07 11:10:15 UTC

Version:           4.8 (using Devel) 
OS:                Linux

Dragging a mail to the folder list, the visual feedback is like I could also drop the mail in between two folders (such as when reordering whole folders).
Of course, this is not possible, so to make the user experience a bit more straight-forward, we shouldn't offer this kind of placement for individual mails, just for folders.

Reproducible: Always



Expected Results:

Comment 1 Laurent Montel 2012-01-19 11:12:40 UTC

I fixed bug when we dnd email and we had a menu to put between folder.
For this bug I am not sure that we can fix it because it's a internal method from qtreeview.

Comment 2 Laurent Montel 2012-02-22 08:03:35 UTC

Fixed in 4.8.1

Comment 3 Bernd Oliver Sünderhauf 2012-06-21 09:18:15 UTC

Using 4.8.3, there is still something like an in-between state.

Comment 4 Bernd Oliver Sünderhauf 2012-11-05 14:26:09 UTC

Still unfixed in 4.9.2

Comment 5 Bernd Oliver Sünderhauf 2012-11-27 01:03:20 UTC

A solution to this problem is described on http://stackoverflow.com/questions/6942098/qt-qtreeview-only-allow-to-drop-on-an-existing-item (3rd comment of answer 1)

Comment 6 Denis Kurz 2016-09-24 18:14:29 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 7 Denis Kurz 2017-01-07 22:28:10 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.