| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Change-Id: I308ac6bc053ed2648802f433e01be92f36e223b8
Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: Ice0f274afe5ca5e5f453bddc3c3b63f44bbef06c
Reviewed-by: Paul Tvete <paul.tvete@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When there is a rotation transformation on a RectangleNode it is not
possible to take advantage of accelerated blitter paths, but we still
need to do custom painting to recreate the behavior of a Rectangle
component in Qt Quick. Now when there is a rotaiton transformation we
will fall back to using QPainter::drawRect as long as there is no border
or radius. If there is a border or radius value set though we will
instead first render to a QPixmap before painting as the standard
behavior of QPainter::drawRect and QPainter::drawRoundedRect does not
match the expected behavior of a QQuick Rectangle item. This fixes the
poor quality of rotated Rectangles at the cost of speed.
The Rotation of any item should still be discouraged for performance
reasons, but at least now Rectangles itmes should look correct when
used.
Change-Id: I3919ad732c9b4354a95e28e8dc09fcefd53f604e
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The existing implementation has both inaccurate drawing of
borders as well as many alignment issues. Much of these
alignment issues are due to our use of floating point sizes
and the integer based nature of blitter hardware. So now
for the Rectangle node we force alignment via the use of
whole numbers. This should be a better compromise of
speed vs accuracy than previously.
Change-Id: I9d8e9d1b3347a99bf0c2ae65ec66c935d8017817
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
|
|
Change-Id: I2fe8df530a687247a9cd7ea12c1d8de79fef506e
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
