Or, can you recommend a better way to diagnose
this problem. (The whole thing needs to be rewritten
now that I am older and wiser, but not just yet.)
I'd try to log calls to update() on the widget, and dump the stacktrack for each
of those to a file. You can do that (at least on gdb) by setting a breakpoint on
it with some commands to run on the breakpoint, after wich you immediately
resume. If you really break, it will be much harder to trace as returning to the
running application afterwards will itself cause a repaint. Run your app for a
bit, and inspect the file to see how your update got called.
There are multiple widgets involved
and my app contains 168 calls to update().
:-)
André
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
