On 03/31/2014 03:24 AM, Till Oliver Knoll wrote:
> Am 30.03.2014 um 22:31 schrieb Brad Pepers<bpep...@me.com>:
>
>> ...
>>
>> Any hints on where to look for this or maybe some other way to code this to
>> avoid the problem?
>
> I don't know where those "extra paint events" come from (or why),
> but the most obvious thing for me would be to set a (conditional?) breakpoint
>in your paint event handler and see from where those calls are triggered, and
under what condition.
>
I know from experience that that does not help.
I'm pretty sure the back trace from paintEvent()
will just lead to the main event loop, not the
cause.
What we all really want to know is:
Which of the previous calls to update() between
point A and now actually scheduled the/a paint event.
Bill
> Probably works best with a Qt debug build ;)
>
> Cheers,
> Oliver
>
> P.S. Yes, I guess you figured out that much yourself - but that's just where
> I would start, too ;)
> _______________________________________________
> 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
