QTableView switching currentIndex not performing as expected

[AlphaWolfXV]

Hello,
Thank you so much for the response. I think I must be confusing something, this works for mouse clicking, it forces back to column 1. However, still on the arrow key behavior I get a dotted line surrounding the column 1 but the selection is still on column 0. Either way this gives me a lot of information to go on. Thank you for that, I missed that I had to implement the superclass to get the desired behavior.
Thank you so much!
AlphaWolfXV

---

Added after 11 minutes:

I made a qDebug to illustrate the behavior is working like it should, just the selection is not updating - I believe the index is correct, just the cell selected is not correct with the key events...

void currentChanged(const QModelIndex &current, const QModelIndex &previous) {
        qDebug()<<"cR:"<<current.row()<<"cC:"<<current.column()<<"pR:"<<previous.row()<<"pC:"<<previous.column();
        QTableView::currentChanged(current, previous);
        if (current.isValid() && current.column() == 0) {
            qDebug()<<"wow, we need to change it..."<<current.row()<<current.column();
            QModelIndex index = current.sibling(current.row(), 1);
            setCurrentIndex(index);
 
            // Or, to move the current item without changing the selected items
             //selectionModel()->setCurrentIndex(index, QItemSelectionModel::NoUpdate);
        }
    }
};

void currentChanged(const QModelIndex &current, const QModelIndex &previous) {
        qDebug()<<"cR:"<<current.row()<<"cC:"<<current.column()<<"pR:"<<previous.row()<<"pC:"<<previous.column();
        QTableView::currentChanged(current, previous);
        if (current.isValid() && current.column() == 0) {
            qDebug()<<"wow, we need to change it..."<<current.row()<<current.column();
            QModelIndex index = current.sibling(current.row(), 1);
            setCurrentIndex(index);

            // Or, to move the current item without changing the selected items
             //selectionModel()->setCurrentIndex(index, QItemSelectionModel::NoUpdate);
        }
    }
};

To copy to clipboard, switch view to plain text mode 

Capture5.jpg

[ChrisW67]

The current item and the selection are two different things. Depending on the selectionMode() and selectionBehavior() set on the view you might get this behaviour regarding the state of the selection after setting the current item, and you might not. That is why I suggested you might want to make the column zero items not selectable in the model to avoid any possibility of them getting into the selection.


If your requirement is that clicking on column 0 sets the currentIndex() but adds the item in column1 to the selection then you have to code that slightly differently.

[AlphaWolfXV]

Hello again,
Thank you for your help. I will review the docs with the different selection modes/behaviors to see what I can come up with. I appreciate all the help, and the push in the right direction.
Just to be clear, to make the column 0 non selectable, we use the item->setSelectable() correct? In other words, make all the items in col 0 not selectable?

Finally just to clarify the end goal, i wanted the view to only select values(items) in column 1. If they click in column 0, the code supplied above works wonderfully. If they arrow key over (Left) to column 0, the selection box stays in col 0 even though I can tell it updates the current index as it is supposed to. I was hoping that when the user hits "left" arrow on keyboard it would "bounce" to col 0 and immediately back to col 1... Not a huge deal, I will continue looking into it.

Again, thank you for all your kind help!
AlphaWolfXV

[ChrisW67]

With an underlying QStandardItemModel yes, you would use item->setSelectable(false) on every item in column zero. In your own QAbstractItemModel subclass you would arrange the equivalent in your QAbstractItemModel::flags() implementation.

[AlphaWolfXV]

Perfect, I will give that a try. Thank you again for your help,
AlphaWolfXV