| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Oops...
Reviewed-by: Jeremy
|
|
|
|
|
|
|
|
|
| |
RFs::GetSystemDrive doesn't exist in 3.1 (even though it is in the
symbian documentation). Moved it to a new function in the S60 plugins.
For 3.1, it returns EDriveC, for all other versions the RFs API is used
Task-number: QT-805
Reviewed-by: Iain
|
|
|
|
|
| |
Task-number: QTBUG-4473
Reviewed-by: Paul
|
|
|
|
|
|
| |
Task-number: QTBUG-3211
Task-number: 236875
Reviewed-by: Alex
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This code is wrong:
if (brush != Qt::NoBrush)
...
It should be:
if (brush.style() != Qt::NoBrush)
...
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
| |
We need to lock before falling back to QRasterPaintEngine
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that one cannot do multiple blits within a double-buffered
surface in overlapping one another without doing a Flip in between. I
find this a little odd and will check that it's the correct behavior but
this fixes bugs in scroll(). To see a case that used to produce drawing
errors check out the collidingmouse example and drag the viewport
around.
Reviewed-by: Jervey Kong <jervey.kong@nokia.com>
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
tests/auto/qtwidgets/tst_qtwidgets.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's no need for the intermediate surface creation. RenderTo will
handle things like palette/transparency etc. Should also provide some
speedup.
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This seems not work correctly on quite a few boards so I'd rather have
people turn it on explicitly.
Reviewed-by: Noam Rosenthal <noam.rosenthal@nokia.com>
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
Conflicts:
tests/auto/qimagereader/tst_qimagereader.cpp
tests/auto/qpainter/tst_qpainter.cpp
tests/auto/qtwidgets/tst_qtwidgets.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The pvr2d.h/wsegl.h headers we ship with Qt (in src/3rdparty/powervr)
are meant for the PowerVR SGX. However, we use an MBX-specific define in
the powervr driver.
Reviewed-by: Jørgen Lind
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the case of optimized animated gifs, we don't want to discard
the contents of the previous frame, this is handled if needed in the
disposal process.
Task-number: 247365
Reviewed-by: Samuel
|
| |/
|/|
| |
| | |
Reviewed-by: Trustme
|
| |
| |
| |
| |
| |
| | |
This function is only exported when DirectFB is built into QtGui.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
When building DirectFB as part of QtGui and not as a plugin this patch
will export two global functions for getting a surface given a widget.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| | |
I had the logic of the assert wrong with the isAncestorOf call.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| | |
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| |
| |
| | |
Partially revert a974ce81d6324d8d85ade0153b5ce7c757ba4fdf. It seems odd
to just ignore the actual data in the input event but when the layer and
the event differs the layer is correct.
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
This will make DirectFB version tests work.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
Avoid warning when building DirectFB as part of Qt.
Reviewed-by: TrustMe
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fix should optimize pixmap loading on most platforms and also fixes
a bug on a certain hardware where the alpha channel of an image was not
retained upon loading it.
This patch also takes care of handling dithering better in
QDirectFBPixmapData::fromImage().
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| | |
It's QT_NO_DIRECTFB.*, not QT_DIRECTFB_NO.*
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
This makes debugging easier.
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we make sure to erase the background to background color in connect()
we don't have to do it in setGeometry.
Also clean up the code in QDBWindowSurface::flush
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
No need to carry those extra bytes around when QT_DIRECTFB_WM is
defined.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| | |
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This code is roughly the same as in other screen drivers. We shouldn't
flush widgets that are in a graphicsscene as a proxy widget. They will
be handled by the graphicsview.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This lets us stream a single QPaintBuffer instead of one QPaintBuffer
per frame in the trace graphicssystem, which leads to not streaming
pixmaps / images once per frame. Performance when doing a trace is also
a lot better for painting heavy applications.
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously we didn't properly compose windows so QT_NO_DIRECTFB_WM mode
would generally only work for single windows (with no popups).
This also simplifies the code a lot. Previously we would among other
things paint the mouse cursor twice in this mode.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This surface is painted every time we move the mouse cursor (in
NO_DIRECTFB_WM) and doesn't change all that often so caching it is
relatively easy and beneficial.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make sure to release the surface of a window before resizing. Seemingly
certain versions of DirectFB change the surface when the window is
resized.
Also clean up setGeometry()
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running an application with graphics system trace everything that
gets painted to the window surface is proxied through a QPaintBuffer,
which is then both streamed to a trace file and replayed on a raster
window surface. The trace file can then be replayed with
tools/qttracereplay to measure pure painting performance.
Reviewed-by: Gunnar Sletta
|
| |
| |
| |
| |
| |
| |
| | |
We should fill the bounding rect only when the region has one rectangle.
Not the other way around.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since DirectFB allows for providing position and size on creation of
windows we might as well use these fields rather than first create the
surface and then resize it.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
DirectFB doesn't let you query the size of the Display in versions prior
to 1.0. In this version require people to specify the size using
QWS_SIZE, QWS_DISPLAY or print a warning and exit.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| | |
Support exporting QWS_SIZE=100x100 to set size
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| | |
DSPD_XOR is not supported until 1.0.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We don't want this surface to be released by QDirectFBScreen. It's
always created without tracking.
Also abstract the if (dfbSurface != primarySurface) things since we will
use it from multiple functions.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
This convenience function will be called from whereever the subsurface
is invalidated.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| | |
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
| |
| |
| |
| |
| |
| | |
sibling exists when QT_NO_DIRECTFB_WM is defined as well.
Reviewed-by: Jørgen Lind <jorgen.lind@nokia.com>
|
| |
| |
| |
| | |
Reviewed-by: Tom
|