Use the debugger to find out where the crash occurs by printing the backtrace.
Use the debugger to find out where the crash occurs by printing the backtrace.
thanks again ;
but i changed my plan , i deleted all the QTablewidgets , no i am using table views with models (QStandardItemModel + QTableView = QTableWidget ) ; it's better !
i have no craches , no problems
i confirm that the problem was in the QTableWidget (many not only one )
sometimes it works , and sometimes all functions cause errors (removeRow , clearContents , setRowCount , setItem , item ...)
and i am not the one , if you look at google you will find a lot of similar problems with this widget !!
so models are better + fast
thanks![]()
another one bites the dustno doubt it requires a bit extra effort, but using proper Model View classes is always the best..and gives you more inside info..soon you'll be pulling towards delegates..and yes, good decision
![]()
Bookmarks