aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/compiler/qv4compiler.cpp
diff options
context:
space:
mode:
authorRichard Moe Gustavsen <richard.gustavsen@qt.io>2019-01-24 14:50:44 +0100
committerRichard Moe Gustavsen <richard.gustavsen@qt.io>2019-01-30 11:04:04 +0000
commit965f49bb4f83c9eedd56f9ec01f166a4634a05d3 (patch)
tree1e75366794ef2389de6448b6afbc90233a68a994 /src/qml/compiler/qv4compiler.cpp
parent8ec2403603f82e7a0d43b4de04c97ef1c7f1ad35 (diff)
QQuickTableView: use QMap instead of a QRect to keep track of loaded columns
TableView keeps track of which rows and columns that are loaded at any point by using a QRect called "loadedTable". loadedTable basically describes the top-left and bottom-right corner of the table that has been loaded (which also is what ends up visible on screen). But now that we prepare for making it possible to hide rows and columns, using just a QRect becomes to simple. A rectangle will only tell what the edges of the table are, but not if any of the rows and columns in-between are hidden and therefore not loaded. So a QRect(0, 0, 10, 10) will give us the impression that we have 10 visible columns on screen, but in reality, we might have a lot less. This patch will change this to instead use two QMaps to record loaded rows and columns. This will make it much more easy to deal with hidden rows and columns in upcoming patches. We use a QMap instead of a QHash/QSet to keep the list of columns and rows sorted, since we frequently still need to know the edges of the table, like before. Change-Id: I45736485c67042403b095e73b5f2effa411281d0 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Diffstat (limited to 'src/qml/compiler/qv4compiler.cpp')
0 files changed, 0 insertions, 0 deletions