| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Change-Id: I3570a6ee87786f1459a922bd43f38d1bbbe2c640
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
Reviewed-by: Paul Tvete <paul.tvete@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ice0f274afe5ca5e5f453bddc3c3b63f44bbef06c
Reviewed-by: Paul Tvete <paul.tvete@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
QtWebEngine always receives 256x256 large tiles, but is being told
which part of the texture should be painted if the content is
effectively smaller on a tile.
Change-Id: Ie979562fb948c853e22155e3f7f3807ae10558ef
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Carry any non-full rect from the layer to QPainter::setWindow.
This is needed by cc::RenderPass::output_rect in QtWebEngine.
Change-Id: I8ffd7f0b7646e664a225df096de455899338d4ba
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Replace negative margin values with 0. Test case:
qtdeclarative/tests/manual/scenegraph_lancelot/data/borderimages/borderimage_rotated_unsmoothed_negative_borders.qml
Change-Id: I53d143fd079cbaa5e6c8080ada81720f8b1b598b
Reviewed-by: Andy Nichols <andy.nichols@theqtcompany.com>
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Id6f986bc5d46912355f42e6ae8d72fe2738c2c19
Reviewed-by: Laszlo Agocs <laszlo.agocs@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise we end up with duplicated symbols when linking
statically.
This partly reverts commit 139ace5b57b82396dc37a6781bfae4a251172764.
Change-Id: I0b33cc00d19e7c541b33a72a7d27e1c0a895d988
Task-number: QTBUG-42679
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The logging categories used in this module are already defined in
qtdeclarative, which this module depends on. We could just use
Q_DECLARE_LOGGING_CATEGORY instead of Q_LOGGING_CATEGORY, but
even simpler is to just include the private header file where
they are already declared.
Change-Id: I5adb0cfc5fd4fed234935820e52d7c7e7a797fae
Reviewed-by: Andy Nichols <andy.nichols@digia.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>
|
|
|
|
|
|
|
|
| |
This issue was fixed in qtdeclarative a slightly different way, so now
we need to change our code to reflect the change.
Change-Id: I5c050da88efc32e808ad5a4a764ff410544db1cd
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
| |
Change-Id: Id4b87c285370182b34ec42cf02c59627e8019956
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
|
|
|
|
| |
There will be times when we hit custom QSGGeometry nodes where we won't
be able to render them. Rather than crashing, just ignore them. The
Q_UNREACHABLE macro was more for the development phase anyway.
Change-Id: I4962cab17b8b3399e081dba58c3a7c4dd988de8f
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
|
|
|
| |
This prevents blending with either garbage or the contents of the
previous buffer when clearing with colors with an alpha.
Change-Id: I52fc13c2af224a37206e51efd38301b95085c9b2
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
| |
Change-Id: Icd2dbadaa0302ceaf06daaeb26b10cb9403cc492
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
|
|
|
| |
There were many cases where properties of nodes could change but since
the node was not marked dirty, the scene update was never rendered.
Change-Id: I7740a43d98521073056f85fe80d6c1ff213236a3
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
If QSGRenderer::renderScene is not called by SoftwareLayer then any
updates in the scenegraph will not be reflected in that layer. This is
the "live" but not "recursive" situation.
Change-Id: If55cc71b3932e283855e3a1f9ff1bca5e07f4498
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
| |
Change-Id: I842c8cd117f1e25cc7848618e86d2aff2e5e522f
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|