38f08eec14
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.7 6.5 Fixes: QTBUG-119076 Change-Id: If699463944ca2abaed8f93a2cd3ea30f33b79145 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io> (cherry picked from commit 57d209c4fdea4766f24479a1f20c2975d34a1a0f) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.