diff options
author | Marcel Schuette <marcel.schuette@nokia.com> | 2012-05-08 09:06:19 (GMT) |
---|---|---|
committer | Qt by Nokia <qt-info@nokia.com> | 2012-05-30 19:47:09 (GMT) |
commit | 9f4f45687bba0e911790bf703e98379d8be1ab65 (patch) | |
tree | cf04696b2fc7457ffea1ea0b4f76a51ac18b354b /translations/qt_help_ja.ts | |
parent | 6c20d552b9917ea736c52a7d436dafbf542bff30 (diff) | |
download | Qt-9f4f45687bba0e911790bf703e98379d8be1ab65.zip Qt-9f4f45687bba0e911790bf703e98379d8be1ab65.tar.gz Qt-9f4f45687bba0e911790bf703e98379d8be1ab65.tar.bz2 |
DirectFB: Improvement for QDirectFBPaintEngine::fill()
Improvement for bug fix related to QTBUG-23850 in QDirectFBPaintEngine:
combine the conditions for an accelerated fillrect (5 elements and
rectangle shape) in first if-statement.
The previous check for NULL pointer solves the problem for the crash,
but it simply skips the type check (which caused the crash before) and
the or-condition (shape) became true and leads to an accelerated
fillrect. Otherwise it would fallback to raster.
The original reason for the crash (elemets is null) might be
Q_DISABLE_COPY macro of QVectorPath, especially with the last lines of
the Q_DISABLE_COPY documentation, which could become true on embedded
devices, where DirectFB is often used, with special
toolchains/compilers.
Task-number: QTBUG-23850
Change-Id: I340291fbce24260c7522684305c292e66cfc32af
Reviewed-by: Girish Ramakrishnan <girish.1.ramakrishnan@nokia.com>
Diffstat (limited to 'translations/qt_help_ja.ts')
0 files changed, 0 insertions, 0 deletions