BasicTableView refactoring: Separate view from user interaction

One of the main tasks of the user interaction code is to manage
the current items selection. However, in the upcoming TreeView,
the selection will be completely different, but we still want to
keep 99% of the view code.

Also, in our TreeView implementation, the user's model is proxyfied
by a TreeModelAdaptor. But that's not the case in the TableView.
So, in order to keep using the same API, we introduce the __model
intermediate property.

Where it makes sense, TableView and TreeView share common API
through BasicTableView.

Change-Id: I0a922c1c1093919df7d880d72fe12ed0f372cc08
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/tests/auto/controls/data/tst_tableview.qml b/tests/auto/controls/data/tst_tableview.qml
index 33599000..b149e76b 100644
--- a/tests/auto/controls/data/tst_tableview.qml
+++ b/tests/auto/controls/data/tst_tableview.qml
@@ -512,7 +512,7 @@ TestCase {
         table.forceActiveFocus();
 
         // to go to next row (this model has 10 rows)
-        table.__incrementCurrentIndex()
+        table.__listView.incrementCurrentIndex()
 
         // read data from the model directly
         var valuefrommodel = table.model.dataAt(table.currentRow)
@@ -541,7 +541,7 @@ TestCase {
         table.forceActiveFocus();
 
         // to go to next row (this model has 3 rows, read the second row)
-        table.__incrementCurrentIndex()
+        table.__listView.incrementCurrentIndex()
 
         verify(table.__currentRowItem !== undefined, "No current item found")
         var label = findAChild(table.__currentRowItem, "label")