Version: (using Devel) Installed from: Compiled sources With sort and aggregation set as follows: Message Sort Order: By Date/Time of Most Recent in Subtree Aggregation: Standard Mailing List Using "Delete Thread" causes the message list focus to jump backwards several threads. The focus should return to the most recent undeleted message to have focus prior to moving to the deleted thread. The random jump backwards in threads causes you to literally lose 'focus' of where you were in the message list.
Hm.. you're right. Theoretically the next thread should be selected but when deleting large threads sometimes it happens that a random thread, usually close to the one being deleted, becomes the current. I suppose that this is caused by a chunked delete operation in that messages are deleted in at least two steps. I'll see what can be done.
SVN commit 978730 by stefanek: A new approach to the choice of the next message to select in place of the ones being deleted. BUG: 195531 BUG: 187297 BUG: 183923 M +3 -0 core/model.cpp M +180 -13 core/view.cpp M +1 -0 pane.cpp M +2 -1 widget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=978730