summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/libtiff/libtiff/tiffio.h
diff options
context:
space:
mode:
authorVolker Hilsheimer <volker.hilsheimer@qt.io>2024-06-17 21:32:28 +0200
committerVolker Hilsheimer <volker.hilsheimer@qt.io>2024-06-18 23:37:17 +0200
commit57d209c4fdea4766f24479a1f20c2975d34a1a0f (patch)
tree77ad7d96c90c3d2e30c2049aa2eea0270b2db5a3 /src/3rdparty/libtiff/libtiff/tiffio.h
parent71d0ea7d042d61e8d42e9cf2700c439d4337345b (diff)
QTableView: optimize selection when spans are presentHEADdev
If a span is selected, we used to assume that rows and columns might be moved, and made a selection with a range for each cell in the span. This resulted in very large selection models. We already had optimized the case that we didn't have any moved rows or columns, skipping the mapping for the respective (or, usually, both) directions and just making a single range. Apply that same optimization for the case where a span exists and intersects with the selection area. Avoid code duplication by only updating the top/left/bottom/right values depending on the configuration of the table, and then create the selection based on those. Adapt the test case; we now get a single range, even when a span is present, and the range includes all cells included in the span. Add a debug streaming operator in the test case, as there is none implemented in QTableWidgetSelectionRange, to ease debugging. That operator can become a hidden friend of QTableWidgetSelectionRange in a follow-up commit. Pick-to: 6.8 6.7 6.5 Fixes: QTBUG-119076 Change-Id: If699463944ca2abaed8f93a2cd3ea30f33b79145 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
Diffstat (limited to 'src/3rdparty/libtiff/libtiff/tiffio.h')
0 files changed, 0 insertions, 0 deletions