| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The is probably not the ideal path (as there is at least one copy), but
we can document that mirror is slow. There is no clear path to blit
mirrored though, so it is better to do this than to render un-mirrored
or use QPixamp.toImage().mirrored().toPixmap()
Change-Id: Ife751f3635e8f9d8ea08676fb1f263bdb727aa2f
Reviewed-by: Lars Knoll <lars.knoll@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>
|
|
|
|
|
|
|
|
|
|
|
| |
By default we used the threaded renderer, but this will
only work if the platform has the capability to render to
QPixmaps from multiple threads. Now if we don't have
the Threaded Pixmaps capability we use the non-threaded
render loop.
Change-Id: I5090e874d0bbdd1e54561ea3583a5a17bbf50061
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
QGradient does not allow stops positions that are outside the bounds of
0 and 1. Gradients created from QML however can have stops outside of
these bounds and so we must normalize these stops before giving them to
QPainter to render. This change creates a new stop at 0 or 1 if a stop
goes below or above the bounds respectively, and interpolates a new
color value for the stop based on the original position.
Change-Id: I10cc41d923e88a9b41bfd27de0326cea25464add
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
|
|
|
|
|
|
| |
Should resolve issues with deployment.
Change-Id: I268734e5db67d3f2bc3afa603618270985387b30
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|
|
Change-Id: I2fe8df530a687247a9cd7ea12c1d8de79fef506e
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
|