QTableWidget::itemSelectionChanged
-
exactly. and in my opinion that's missing in the documentation.
or even wrong in general -
@Megamouse
Well it might be border case and hence the slightly odd behavior.
Since we are using SingleSelection, the dragging is really not needed as user
can just click on the one he wants. -
Well.
I use the selection as a direct visual indication.
Meaning if you change the list object the view will show corresponding data on another table.So if i were to use currentrow in this case the data would be wrong.
-
Well did you try the signal for that. seems to be correct even
when ui->listWidget->currentRow() is off. ? -
don't worry about it. It's fixed anyway. I just think it's a weird glitch or "feature"
-
indeed it is.
-
@Megamouse
native events!
How did you find it? where they announced something like that?
but thank you ... you saved my life ;) -
@HojjatJafary It was on a hunch. After searching for native event problems for a while, I found an issue on the Qt issue tracker in which the solution to the bug was shared in the comment section.
-
Can you share the link to the bug report ?
-
I believe it's https://bugreports.qt.io/browse/QTBUG-69074
-
@SGaist sorry I wasn't on this forum in a while. But Sergio's link is correct