View Single Post
Old 07-22-2026, 04:32 PM   #15
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 9,858
Karma: 7500000
Join Date: Nov 2009
Device: many
I have been reading and trying to understand where in the QStandardItemModel dropMimedata routine in Qt's source, the assumption that it must be contiguous comes into play but do not really see it. That source is quite involved as it must work in any QTreeView structure.

If we are 100% sure a simple single move and back will fix the issue, perhaps we could create a workaround that does that immediately after any drop. It is an idea to explore.
KevinH is offline   Reply With Quote