ghorwin
29th October 2007, 04:27
Hi there,
there seems to be a bug in the QTableWidget that causes a crash/access violation and can be reproduced as follows:
- start editing a row in a QTableWidget
- before leaving the editor, start a function that accesses the content of the table widget using the item() member function
The crash occurred when editing a QTableWidget and saving (the save operation reads the data from the QTableWidget by retrieving QTableWidgetItems via the item() member function) while in the in-place editor was still active.
A workaround is to first place the focus on a different widget to finish the editor and than start reading the content of the table widget.
Is this a known bug?
Bye,
Andreas
there seems to be a bug in the QTableWidget that causes a crash/access violation and can be reproduced as follows:
- start editing a row in a QTableWidget
- before leaving the editor, start a function that accesses the content of the table widget using the item() member function
The crash occurred when editing a QTableWidget and saving (the save operation reads the data from the QTableWidget by retrieving QTableWidgetItems via the item() member function) while in the in-place editor was still active.
A workaround is to first place the focus on a different widget to finish the editor and than start reading the content of the table widget.
Is this a known bug?
Bye,
Andreas