On Jun 10, 2012, at 3:34 PM, Jelmer van der Linde wrote:
> On Sunday 10 June 2012 at 15:14, Till Oliver Knoll wrote:
>> A further attempt to narrow down the issue could be to try different
>> paint engines ("raster" or "native"): AFAIK up to Qt 4.7 the "native
>> painter" was used, but it could be
On Sunday 10 June 2012 at 15:14, Till Oliver Knoll wrote:
> A further attempt to narrow down the issue could be to try different
> paint engines ("raster" or "native"): AFAIK up to Qt 4.7 the "native
> painter" was used, but it could be that it was now (Qt 4.8) switched by
> default to the "raster
Am 09.06.12 11:06, schrieb Daniël de Kok:
> On Jun 8, 2012, at 2:44 PM, Jelmer van der Linde wrote:
> ...
> Since, this bug does not occur with Qt < 4.8 on OS X and any Qt 4 version on
> Linux or Windows, we suspect that this is a bug specifically in Qt 4.8 on OS
> X.
A further attempt to narro
On Jun 8, 2012, at 2:44 PM, Jelmer van der Linde wrote:
> It is only when I scroll that Qt doesn't invalidate the the old drawing area.
> As if the position changes due to scrolling aren't taken into account when
> invalidating the old rect.
Also see the workaround that Jelmer referred to: the
Hello Jordi,
If I increase the size of the rectangle boundingRect returns, it does correctly
clear that area. But my bounding rectangle is already as large (or just for
testing, larger than) the actual tooltip.
It also only occurs when I scroll. If I move the mouse (and therefore
reposition t
Hi Jelmer,
Just a clue, without looking at your code : ensure your tooltip's
bounding rect is greater than the tooltip itself. I mean ALL the
tooltip, text and grey-box-background.
This error appears when you don't take care of this. QGraphicsView only
invalidates the rect returned by the method
Hello,
I get drawing issues when I simultaneously scroll and track the mouse
to let a (home made) tooltip follow it. It looks as if Qt fails to
track which part of the image should be redrawn. (screenshot:
http://dl.dropbox.com/u/6635118/Screen%20Shot%202012-05-18%20at%2013.04.21.png)
Is this a b