View Single Post
Old Today, 10:29 PM   #56
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,901
Karma: 7500000
Join Date: Nov 2009
Device: many
Yes, the order you select a multi-selection actually impacts how it works. Qt treats a contiguous click and shift-click of n items different from that done on n-1 items followed by a single add-on to reach n contiguous items. It is differently reported by Qt.

So unlike single-click selection, how the user actually selects a multiple selection (in pieces vs totally matters and order does matter.

So if you want to build up a region by individual clicks and not a single click-shift-click it will will impact the result that Qt reports the user's selections.

That is why I had to rebuild the selection to form normal ranges to get the follow-on move right to work at all.

I will look into replacing all of Qt's internal selection mechanism with my own to try to properly make it selection order independent just like I already did for the reselection issue that broke move right.
KevinH is offline   Reply With Quote