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. ? -
indeed it is.
-
Can you send me the sample you use?
For the nativeevent:
Apparently it is already fixed for Qt 5.11.2.
But to explain:
One of the devs added a copy pasta mistake and now we need to cast the nativeEvent messages like this for Qt 5.11.1:#if (QT_VERSION == QT_VERSION_CHECK(5, 11, 1)) MSG* msg = *reinterpret_cast<MSG**>(message); #else MSG* msg = reinterpret_cast<MSG*>(message); #endifFor some programs this breaks the whole application
@Megamouse
native events!
How did you find it? where they announced something like that?
but thank you ... you saved my life ;) -
@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 ?
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
I believe it's https://bugreports.qt.io/browse/QTBUG-69074
