| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
GetSurface() was checked for NOT returning DFB_OK, but it should
Merge-request: 2528
Reviewed-by: Marcel Schuette <marcel.schuette@nokia.com>
|
|
|
|
|
|
|
|
|
| |
already premultiplied in the image.
This also avoids the temporary surface and blitting.
Merge-request: 990
Reviewed-by: Marcel Schuette <marcel.schuette@nokia.com>
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
| |
Merge-request: 931
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
|
|
|
|
|
| |
Fix minor stylistic issue raised by Oswald
Removed duplicate sourceSurface pointer introduced by sibling merge request
|
|
|
|
|
|
| |
Merge-request: 915
Reviewed-by: Donald Carr <donald.carr@nokia.com>
(cherry picked from commit b62079cf17044e09999eb1808788926ea921fb05)
|
|
|
|
|
|
|
|
|
| |
An IDirectFBSurface can have an alpha channel for an opaque QPixmap.
This change will make sure we don't blend unless QPixmap::hasAlpha
returns true.
Merge-request: 913
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inspired/rewrite of Denis Oliver Kropp's merge request
(http://qt.gitorious.org/qt/qt/merge_requests/874)
When blitting premultiplied source surfaces one has to set
DSBLIT_SRC_PREMULTIPLY.
This also reverts the erroneous 6acbf6dce98903310023284e27a65c19f9a829bc
Merge-request: 903
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
| |
Windows with Qt::WA_NoSystemBackground should clear to transparent in
beginPaint.
Merge-request: 882
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
| |
Merge-request: 844
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These functions can be a big help in debugging rendering errors in an
application and can even be handy to use for real functionality. While
it requires the app to explicitly link to the plugin (when compiling
with -plugin-gfx-directfb this is still much better than not exporting
them).
Since this was the only use-case for QT_DIRECTFB_PLUGIN it's probably
better to take that define out.
Merge-request: 2470
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt and DirectFB have different definitions of SourceOver. In DirectFB
it's defined as this:
/* pixel = (source * fs + destination * fd),
sa = source alpha,
da = destination alpha
*/
DSPD_SRC_OVER = 3, /* fs: 1.0 fd: 1.0-sa */
In other words, the source pixels are not multiplied by the alpha and
this leads to issues with RGBA values like 255, 0, 0, 0.
The composition mode that in DirectFB that maps onto Qt's
CompositionMode_SourceOver is DSPD_NONE, defined like this:
DSPD_NONE = 0, /* fs: sa fd: 1.0-sa (defaults) */
Merge-request: 807
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Being able to debug which paint operations are slow with Qt/DirectFB is
currently only possible in debug builds (which defeats the purpose
somewhat) or by frequent recompilation (with different defines).
This patch cleans up the mechanism somewhat and makes it available in
release builds as well.
The overhead is a single int comparison so it really isn't a performance
issue to have this code in place at all times.
Reviewed-by: Anders Bakken <agbakken@gmail.com>
|
|
|
|
|
|
|
| |
Don't try to read the text length more than once.
Task-number: QTBUG-9977
Reviewed-by: Jørgen
|
|
|
|
|
| |
Task-number: QTBUG-11542, QTBUG-11196
Reviewed-by: Jørgen
|
|
|
|
|
|
|
|
|
| |
Every image that was converted with flags & Qt::NoOpaqueDetection would
be considered to have an alpha channel. This patch fixes that and
simplifies the code a little.
Merge-request: 637
Reviewed-by: Samuel Rødal <sroedal@trolltech.com>
|
|\
| |
| |
| |
| | |
Conflicts:
translations/translations.pri
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The PowerVR screen driver was using QTransformedScreen::tranformation()
which is in a class that is Q_AUTOTEST_EXPORT. That means that it would
only work with a developer build. This contributed patch changes it to
QScreen::transformOrientation() instead which is Q_GUI_EXPORT.
Task-number: QTBUG-10193
Reviewed-by: Lorn Potter
|
| |
| |
| |
| |
| |
| |
| | |
Fix comes from the bug report.
Task-number: QTBUG-9532
Reviewed-by: Tom
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
mkspecs/common/symbian/symbian.conf
qmake/generators/symbian/symmake.cpp
src/3rdparty/webkit/WebCore/WebCore.pro
|
| |
| |
| |
| |
| |
| |
| | |
Clean up the function a little and make sure I don't call
QImage::hasAlphaChannel twice for opaque images.
Reviewed-by: muthu <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
We don't need to do the conversion using QImage when NoOpaqueDetection
is specified.
Reviewed-by: muthu <qt-info@nokia.com>
|
|\ \
| |/
| |
| |
| | |
Conflicts:
src/gui/styles/qs60style_s60.cpp
|
| |
| |
| |
| |
| | |
Task-number: Related to QTBUG-5117
Reviewed-by: Jørgen Lind
|
| |
| |
| |
| |
| |
| | |
QList<T>::remove() is QT3_SUPPORT, replace with erase().
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since DirectFB always uses the front buffer of a double buffered surface
as the source when blitting we needed to make sure that the front buffer
was valid and hence we called Flip for each scroll. This had negative
performance impacts since you could end up with various parts of a
window being updated at different times.
With this patch we store whether the front-buffer is up to date inside
the window surface and only call Flip in scroll if it's not.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
DirectFB will print a warning for this since the file doesn't exist but
we might as well not try when we know the file doesn't exist.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.exe
examples/multimedia/audioinput/audioinput.cpp
src/corelib/io/qfsfileengine.cpp
src/gui/egl/qegl_wince.cpp
src/gui/egl/qeglproperties.cpp
src/gui/egl/qeglproperties_p.h
src/gui/embedded/directfb.pri
src/gui/kernel/qapplication_win.cpp
src/gui/painting/qdrawutil.cpp
src/opengl/qgl_p.h
src/sql/drivers/odbc/qsql_odbc.cpp
src/sql/drivers/odbc/qsql_odbc.h
tests/auto/auto.pro
tests/auto/qgl/tst_qgl.cpp
translations/assistant_adp_ru.ts
|
| |
| |
| |
| |
| |
| | |
DSPF_DST was added in 1.2.9, not in 1.2.0
Reviewed-by: muthu <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
If you call fillRect(QBrush(QColor())); we should short-circuit before
falling back to the raster engine.
Reviewed-by: muthu <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If you specify an operation that is not recognized in
QT_DIRECTFB_WARN_ON_RASTERFALLBACKS or
QT_DIRECTFB_DISABLE_RASTERFALLBACKS
Reviewed-by: muthu <qt-info@nokia.com>
|
| |
| |
| |
| |
| | |
Task-number: QT-1849
Reviewed-by: Jeremy
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow people to control whether or not to warn on/disable raster
fallbacks using the following mechanism:
export QT_DIRECTFB_DISABLE_RASTERFALLBACKS="draw_pixmap|draw_text"
export QT_DIRECTFB_WARN_ON_RASTERFALLBACKS="draw_lines"
It's still possible to define QT_DIRECTFB_WARN_ON_RASTERFALLBACKS to
something for legacy reasons.
The environment variable check is only available in debug mode.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It seems that I have to premultiply the colors I pass to
IDirectFBSurface->SetColor when composition mode != Source|SourceIn.
It now seems to behave the same way as the raster engine which I guess
should be considered the authority on this matter.
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Qt heuristics say that a QPixmap becomes an alpha pixmap when filled
with a color with alpha != 255 but not that it returns to being opaque
when filled with a color with alpha == 255
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
| |
| |
| |
| |
| |
| | |
This porter duff rule was added in DirectFB 1.2
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
qmake/generators/symbian/initprojectdeploy_symbian.cpp
qmake/generators/symbian/symmake_abld.h
|
| |
| |
| |
| |
| |
| | |
If DirectFB fails to lock a surface it won't necessarily set mem to 0.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If you're only updating parts of a widget we have to make sure
DSFLIP_BLIT is included. Otherwise Qt's assumptions about the backing
store breaks.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Certain boards do not properly support IDirectFBSurface->Flip() with a
partial DFBRegion passed in.
This problem can be worked around by exporting:
QWS_DISPLAY=directfb:nopartialflip
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
This was already possible in non-WM mode. I now enable using the
same connect argument to make it work for WM.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since we don't have a dedicated function that gets called when isOpaque
changes for a window we do not support making an existing window
non-opaque at runtime. Supporting this would require considerable
overhead per flush and we do not want that.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
| |
| |
| |
| |
| |
| | |
The logic was reversed.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|\ \
| |/
| |
| |
| | |
Conflicts:
tests/auto/qlineedit/tst_qlineedit.cpp
|
| |
| |
| |
| |
| |
| |
| | |
This function is only exported when DirectFB is built as part of
libQtGui.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|\ \
| |/
| |
| | |
qstatictext-4.6
|
| |
| |
| |
| | |
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|/
|
|
| |
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
| |
This is a very operation in DirectFB and saves a fair bit of overhead.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|