diff options
author | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2012-04-02 09:59:04 (GMT) |
---|---|---|
committer | Qt by Nokia <qt-info@nokia.com> | 2012-04-16 20:25:06 (GMT) |
commit | 1d95d8b608d5f689afd3c40535ab67ffabb343e9 (patch) | |
tree | e7ceaa850586e562f166a791bc176a3ba2e3bf11 /src/gui/s60framework/qs60maindocument.h | |
parent | e786478d64f6ace802e103a54783784572048864 (diff) | |
download | Qt-1d95d8b608d5f689afd3c40535ab67ffabb343e9.zip Qt-1d95d8b608d5f689afd3c40535ab67ffabb343e9.tar.gz Qt-1d95d8b608d5f689afd3c40535ab67ffabb343e9.tar.bz2 |
widgets/qpa: Fix painting to a fully transparent top level widget
QWS used to have a line to change the composite mode from SourceOver
to Source for the top level widget. This wasn't used with QPA and I
removed the internal DontSetCompositionMode in qtbase. It turns out that
the QWS way is the most efficient one to initialize the background of
the widget.
The alternative is to have the QPlatformBackingStore::beginPaint
always clear the entire to be painted area and then paint the background
of the widget. The difference of painting each pixel once or twice is
noticable on embedded platforms and in the range of one to two fps.
This does come from Qt5. The change removes the hasFeature test as
CompositionMode_Source is available for all backends.
Reproduce the issue with:
echo "QWidget {background: transparent}" > style.css
./examples/widgets/wiggly/wiggly -stylesheet style.css
Task-number: QTBUG-24526
Change-Id: I3e3f8a263cd3cf9dec8628ca8a3bb28c70572121
Original-Id: Ica4c980bb3bf6eb87ddb5b510ac7493292d01543
Reviewed-by: Samuel Rødal <samuel.rodal@nokia.com>
Reviewed-by: Girish Ramakrishnan <girish.1.ramakrishnan@nokia.com>
Diffstat (limited to 'src/gui/s60framework/qs60maindocument.h')
0 files changed, 0 insertions, 0 deletions