QTableWidget Design & Thread Safety Question

[jacek]

I am just curious... is it a bad idea for different threads to modify data in a QTableWidget's QTableWidgetItem if each thread never accesses another threads QTWI?

It's a Very Bad Idea(tm). All widgets belong to the GUI thread and it's very jealous about it.

I have a QTimer that is running, I was thinking that is what I could use to repaint the table.

You can use QTimer to poll the threads or you can make threads send signals/event when data changes. Everything depends on the number of updates per second. If thread will send more than 25 signals per second the polling aproach might be more efficient. On other hand threads can send only changed data, while with polling approach you will have to check all the data.