diff options
| author | Noah Davis <noahadvs@gmail.com> | 2024-01-27 10:10:10 -0500 |
|---|---|---|
| committer | Noah Davis <noahadvs@gmail.com> | 2024-01-30 21:28:19 +0000 |
| commit | a4f44e06988e91c21c85e0e9f29d656d61f9c68e (patch) | |
| tree | 029a60d9a62368e65d3fd872f4ff07f2d2582c38 /src/opengl/qopenglframebufferobject.cpp | |
| parent | c6aa399d062c8b31c2ab88acf564a24cdff7b3c8 (diff) | |
QPainterPath: Fix boundingRect and controlPointRect ignoring start point
The boundingRect and controlPointRect did not use the start point from
the `QPainterPath(const QPointF &startPoint)` constructor until the
`dirtyBounds` or `dirtyControlBounds` member variables were set to true.
Those two are false on construction. This bug was fixed by adding a new
constructor for QPainterPathPrivate that initializes the `elements`,
`bounds` and `controlBounds` member variables with the start point from
the constructor.
There is also an autotest to verify that the top left of the
boundingRect and controlPointRect are at the same position as
elementAt(0) when the start point constructor is used.
[ChangeLog][QtGui][QPainterPath] boundingRect() and controlPointRect()
now use the start point from QPainterPath(const QPointF &startPoint).
Pick-to: 6.7 6.6 6.5
Change-Id: I7bf30364406c14ed60f75d24b78a9a5535f75d93
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Diffstat (limited to 'src/opengl/qopenglframebufferobject.cpp')
0 files changed, 0 insertions, 0 deletions