[Kst] [Bug 121068] Arrow view objects not always clipped correctly
arwalker at sumusltd.com
Thu Mar 30 02:59:29 CEST 2006
I was talking about the _geom QRect. I would hope that a QRegion
that is really just a QRect would be very close in performance
as the native QRect (assuming Qt wrote the code in a clever way).
The only problem I'm aware of the line/arrow problem in Kst with
my previous fix (now reverted) was that you can hover over parts
of the arrow and not set the focus. This is because the findChild
and findDeepestChild use the _geom to detect the focus. Is there
any reason that they don't use the clip region, in which case this
problem goes away?
From: George Staikos [mailto:staikos at kde.org]
Sent: Wednesday, March 29, 2006 4:29 PM
To: kst at kde.org
Subject: [Kst] [Bug 121068] Arrow view objects not always clipped
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From staikos kde org 2006-03-30 02:29 -------
On Wednesday 29 March 2006 18:21, Andrew Walker wrote:
> ------- The full solution for this would seem to require that we move from
> QRect to QRegion. This would allow us to properly define the region that a
> line, ellipse and other non-rectangular objects occupy.
Which QRect? QRegion is quite expensive btw. I tried to avoid it
Kst mailing list
Kst at kde.org
More information about the Kst