| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
checksdk -list now displays the list of available SDK without yielding
the warning message "No SDK specified: Defaulting to ...".
Reviewed-by: mauricek
|
| |
| |
| |
| |
| |
| | |
Reviewed-by: thartman
function declaration was missing arguments as done in the other testcases in 831d2742b7c41924f052acd81620e8bfc58afde7
|
| |
| |
| |
| | |
Reviewed-by: jbache
|
| |
| |
| |
| |
| |
| | |
Reviewed-by: joerg
QTest::newRow only accepts char* and without Qt3Support there is no implicit cast available.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There was a regression in the background color for QComboBox popups.
This should resolve it. It essentially tells the system to stay off
the system palette while QGtkStyle is used. We will introduce
a cleaner style hint for this in 4.6.
Reviewed-by: nrc
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change shows a limitation in Graphics View caused by QPen's
default width being 0 (cosmetic), while Graphics View actually
does not support cosmetic pens at all. Because items are at risk of
drawing lines that poke 1 pixel outside their bounding rect,
QGraphicsView must look for items that are up to one pixel
larger than their bounding rect mapped to viewport coordinates.
Furthermore, mapToScene(QRect) forces us to adjust the
input rectangle by (0, 0, 1, 1), because it uses QRect::bottomRight()
(etc) when mapping the rectangle to a polygon (which is _wrong_). Since
this behavior has been there since 4.2, we don't want to fix it in
a 4.5 patch release...
The only _proper_ fix to this problem is for the view to know the item's
"adjust" in device coordinates, allowing items to use cosmetic pens
freely. Fex, we could introduce QGraphicsItem::viewportMargins() or so.
Added an autotest to ensure this doesn't break again.
Reviewed-by: bnilsen
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
0aa2ef27249dc8e782c2942340776bb19de80a0d
RevBy: TrustMe
AutoTest: tst_QGraphicsItem::boundingRegion() pass again
Details: The original code adjusted the QRect version of a mapped bounding rect,
wheras my patch adjusted a mapped bounding rect (QRectF) and then
converted it to a QRect.
|
| |
| |
| |
| |
| |
| |
| |
| | |
RevBy: Andreas
AutoTest: Still pass
Details: QRectF::intersects does not work with flat rectangles, so
we cannot intersect the bounding rect without adjusting it
first.
|
| |
| |
| |
| |
| | |
RevBy: Olivier
AutoTest: Still pass
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RevBy: Andreas
AutoTest: tst_QGraphicsView::itemAt2 pass again
Details: A QPoint in the view has to be mapped to a pixel in the
scene, otherwise it won't be possible to e.g. click
on items that are smaller than a pixel.
So...we have to optimize the hit-testing code in another way
|
| |
| |
| |
| |
| | |
RevBy: Andreas
AutoTest: included
|
| |
| |
| |
| |
| |
| | |
We can shortcut quite some calculations for the common case
by first checking whether the point is contained in the
control point rect.
|
| |
| |
| |
| |
| | |
Implement specialized (and more efficient versions) of item_helper()
and child_helper() that test for QPointF in the scene.
|
| |
| |
| |
| |
| | |
AutoTest: Still pass.
Details: It's easier to read and understand the code now.
|
| |
| |
| |
| |
| |
| |
| |
| | |
AutoTest: Still pass.
Details: Update requests can be discarded if the item itself is
clipped away and the item clips all its children to shape.
This cut-off is extremely effective (and aggressive:))
|
| |
| |
| |
| | |
AutoTest: Still pass
|
| |
| |
| |
| | |
AutoTest: Still pass
|
| |
| |
| |
| | |
Details: It's clipped away regardless.
|
| |
| |
| |
| | |
RevBy: TrustMe
|
| |
| |
| |
| |
| |
| |
| | |
AutoTest: Still pass
Details: Get rid of QTransform::inverted()/operator*= and do
nothing if the item clips all its children and the update
rect is outside the bounding rect.
|
| |
| |
| |
| |
| |
| |
| |
| | |
AutoTest: Still pass.
Details: Update requests can be discarded if the item itself is
clipped away and the item clips all its children to shape.
This cut-off is extremely effective (and aggressive:))
|
| |
| |
| |
| | |
RevBy: Andreas
|
| |
| |
| |
| | |
RevBy: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| | |
RevBy: Andreas
AutoTest: still pass
Details: Adds emptyClipPath bit, a cut-off to test if the item
has an empty clip path (i.e., is clipped away). Also adds
code for invalidating the cache from inside setPos().
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
RevBy: Olivier
AutoTest: Still pass.
Details: Items usually don't have effective opacity, i.e. it is 1.0, so
don't bother doing fuzzy compare if that's the case.
|
| |
| |
| |
| |
| | |
RevBy: TrustMe
Details: ...otherwise it'll be empty and too much will be clipped away.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Make sure we use the rect-variation of QGraphicsScene's item lookup
functions if the view has a simple transform and a simple expose
region.
Reviewed-by: Bjoern Erik Nilsen <bjorn.nilsen@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RevBy: Alexis
AutoTest: Still pass
Details: findItems() does almost exactly the same as
QGraphicsView::items, the only difference is that it checks
whether we are about to redraw all items. Next step
is to optimize the items_helper functions.
The patch does also include a fix for
::items/childItems_helper(const QPainterPath ...); it didn't
take Qt::Intersects/ContainsItemBoundingRect into account
(in the same fashion as we do in the other helper functions).
|
| |
| |
| |
| |
| |
| | |
RevBy: Alexis
AutoTest: Still pass
Details: No-brainer.
|
| |
| |
| |
| |
| | |
RevBy: bnilsen
AutoTest: All pass + plasma ok
|
| |
| |
| |
| |
| |
| |
| |
| | |
RevBy: bnilsen
AutoTest: Bench
Details : if we come from setPosHelper (so itemChange) we don't need to do all the stuff regarding the size in setGeometry because the size doesn't change.
I remove two calls to fullUpdateHelper and update() because prepareGeometryChange already call updateHelper and setPosHelper call fullUpdaterHelper too so we don't need to call them inside setGeometry.
We can only call prepareGeometryChange only if we don't come from setPos.
|
| |
| |
| |
| |
| |
| | |
RevBy: Andreas
Details: Use QPainterPath::addRect() rather than addPolygon() and
closeSubPath().
|
| |
| |
| |
| |
| | |
RevBy: Andreas
AutoTest: Still pass
|
| |
| |
| |
| |
| | |
RevBy: Andreas
AutoTest: tst_QGraphicsItem::opacity still passes
|
| |
| |
| |
| |
| |
| |
| | |
Task: none
RevBy: Samuel
AutoTest: Still pass
Details: Please do not perform (potentially expensive) calculations just for fun :)
|
| |
| |
| |
| | |
Details: Be a little bit smarter before doing *= :)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Task: none
RevBy: Ariya Hidayat
AutoTest: Still pass.
Details: QTransform::type() is cached, so only the first call to it
should be expensive. However, it is not inlined so there's
an overhead involved (especially when these functions are
called a gazillion times).
|
| |
| |
| |
| |
| |
| | |
RevBy: Andreas
Details: Note that isNull() implies isEmpty(), but it only catches
the cases where width and height is 0.
|
| |
| |
| |
| |
| |
| | |
Details: Checking for QRect::isNull() was wrong in the first place, and
checking for isEmpty()/isNull() is overhead after
4a491a84aeba68279927597a261522dcc23bb3ff.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Details: Those cut-offs are extremely important. After few seconds
interaction with the iphone demo, updateRect() was called
approx. 3000 times with an empty rect. Then imagine what
happens when having e.g. FullViewportUpdate. We do
q->viewport()->update() JUST FOR FUN!
|
| |
| |
| |
| |
| |
| |
| |
| | |
Task: -
RevBy: Andreas
AutoTest: -
Details: Accumulate the parentToItem transform as we iterate instead of
creating it from bottom-up each time.
|
| |
| |
| |
| |
| |
| |
| | |
QFileSystemModel::filter().
Task-number: 250285
Reviewed-by: Benjamin Poulain <benjamin.poulain@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
mkdist doesn't case-insensitive comparison.
Reviewed-by: TrustMe
BT: yes
|
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise, for people who install Qt (everyone outside Nokia), the
animation file isn't present.
Reviewed-by: Trust Me
BT: yes
|
| |
| |
| |
| | |
Reviewed-by: jasplin
|
| |
| |
| |
| |
| |
| |
| | |
desktop environment.
Task-number: 250338
Reviewed-by: Jens Bache-Wiig <jbache@trolltech.com>
|
| |
| |
| |
| |
| |
| |
| | |
Use qmake -query QT_INSTALL_HEADERS at test startup time instead of
relying on the dead QTDIR environment variable.
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
|
| |
| |
| |
| |
| |
| | |
Remove unused QTDIR tests.
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
|