| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Some options were added for 0.9.23. This change adds some ifdefs so DFB
0.9.22 compiles
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
| |
Not sure to what extent it actually works but atleast it compiles now.
- A couple of image formats doesn't exist in 0.9
- IDirectFBSurface::ReleaseSource doesn't exist in 0.9
- IDirectFBWindow::SetBounds doesn't exist in 0.9
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
QSvgIOHandler::canRead() only looked at the 80 first bytes in a SVG
file when looking for the <svg> tag. That tag can obviously be found
at an arbitrary offset from the start of the file, depending on
e.g. comments tags.
Task-number: 255419
Reviewed-by: Kim
|
|
|
|
|
|
| |
We need to set alpha to the right value when copying pixmaps.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
| |
The batch-blits buys us nothing and this is much more readable.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
| |
DirectFB and Qt treats these things rather differently so the mapping
just doesn't work very well. Only use DirectFB for SourceOver stuff
(which is the default mode anyway)
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
| |
Previously we allowed RGB32 but forced fallbacks for all drawing
operations. It turns out blitting operations doesn't work right either
so we'll rather just disallow this format altogether. See also
36ae58e7a6a888d3ae7bd162d59daada550bbfb1
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
Due to incompatibilities between RGB32 in DirectFB and Qt we can't use
RGB32.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
| |
Explicitly cast to integer.
Reviewed-by: Shane McLaughlin <Shane.McLaughlin@trolltech.com>
|
| |
|
|
|
|
| |
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
| |
Q_ACCESSIBLE_OBJECT was missing
|
|
|
|
|
|
| |
Since this is C there are no constructors.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
QDirecttFBPixmapData => QDirectFBPixmapData
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an application calls QIcon::actualSize() for SVG based icons, before
the icon is drawn for the first time, the actualSize() call will
result in the SVG file being loaded and parsed for each call.
Instead of doing that, just render a pixmap of the queried size and
then the resulting actualSize() calls will used the size of the
cached pixmap.
Task-number: related to 251106
Reviewed-by: Kim
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
Include info on the primary surface pixelformat.
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
We're just printout out the integer value anyway.
Reviewed-by: TrustMe
|
|
|
|
|
| |
Needed for fallback warnings
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
| |
Put all variables in the same area for QDirectFBPaintEnginePrivate. Make
QDirectFBPaintEngine a friend.
Also, do away with setClipDirty and replace it with d->clipDirty = true;
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
Move private functions to the bottom of the file to be more in line with
how most qt cpp files are structured.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
| |
Make image caching a lot cleaner and more sensible.
By default we do not cache images since creating a preallocated surface
is quick and we don't really want to waste memory. In the case where the
driver does not support preallocated surfaces you can enable image
caching to speed up drawImage.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
| |
Store whether qt was built with qt3support enabled in .qmake.cache. We
need this info to decide if QT3_SUPPORT should be defined when we
include qimage_p.h. Otherwise we get data corruption issues since the
size of struct in Qt is larger than the one we include in libqdirectfb.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
| |
Made SurfaceCache entirely inline for better readability.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
| |
Store the memory address of our last QRasterBuffer::prepare() call to
make sure we reprepare if someone has unlocked and locked the device
behind our back.
Also optimize QDirectFBDevice::memory() since it might get called a fair
bit.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
| |
Fall back to raster engine when using a transform with
m11 < 0 || m22 < 0.
Task-number: 252921
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
Format the debug info on blitting, drawing and acceleration capabilities
better.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
| |
Allow setting of a QMAKE_INCDIR_POWERVR in the mkspec to specify where the
pvr2d.h & wsegl.h files are located. Set to src/3rdparty/powervr to use
the headers distributed with Qt (for SGX-based SoCs).
Reviewed-by: Trustme
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The PowerVR driver on Qt for Embedded Linux needs to use Imagination
Techologies' proprietary pvr2d & wsegl APIs. These are the headers for
those APIs, allowing the powervr driver to be built. Ideally, these
headers would be provided as part of the SDK supplied by chipset vendors.
For now, we include these headers to let people get going with the
driver.
Licence headers were approved by legal for inclusion into Qt, after some
negotiation with ImgTec (who have also approved their inclusion into
Qt). The headers have also passed a scan by Talko, provided the licence
headers aren't touched.
Reviewed-by: Paul
|
|
|
|
|
|
|
| |
This helps avoid confusion between IDirectFBSurface and
QDirectFBSurface.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
From benchmarking I've established that surface->Lock(DSLF_READ) is
faster than surface->Lock(DSLF_WRITE) which is faster than
surface->Lock(DSLF_READ|DSLF_WRITE).
This patch will make us Lock for read only, when possible.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
| |
export QWS_DISPLAY=directfb:boundingrectflip to enable calling Flip on
the bounding rect of the dirtied area rather than each dirty rectangle.
This could be faster if you update many small rectangles.
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
Qt's coding style => Object *ptr, not Object* ptr
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
Print out detailed information about acceleration mask, blitting flags
and drawing flags when passing debug.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
Clean up code and make it possible to set more DFBSurfaceCapabilities on
the primary surface.
Also allow users to force systemonly for the surfaces.
|
|
|
|
|
|
|
|
| |
Since I am taking a copy of the description anyway it makes sense to
just pass this light-weight object in as a copy rather than a const
pointer.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
| |
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
d->clip() might return 0 at this point so make sure we check before
accessing it.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
| |
Make code more readable by not chaining to QScreenCursor for hide/show.
Since hwaccel is true we don't need the exposeRegion call anyway.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
| |
The enabling/disabling of the Cursor belongs in the
QDirectFBMouseHandler class and not in the QDirectFBScreenCursor. Even
if we use the Qt software cursor we need the events to come in from the
mouse handler.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
| |
Refactor cursor management code to do. No need to change the cooperative
level four times for each show/hide. Simplify code a little.
Also we used to disable the cursor when we wanted to hide it which meant
that we no longer received mouse events.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
Instead of having multiple bool QDirectFBScreen::.* getters I added
DirectFBFlags QDirectFBScreen::directFBFlags() function.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is currently the only way I can make QGraphicsView not have to fall
back to the raster engine for all operations. It seems the QRegion
passed to the paintEvent of QGraphicsView also is set as the systemClip
which in the end makes the QRasterPaintEngine's clipRegion equal the
systemClip. By exporting QWS_DISPLAY=directfb:ignoresystemclip you can
now draw without having a complex clip and therefore take advantage of
hw acceleration with DirectFB.
Reviewed-By: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow programmers to select which operations they want to warn
on/disable and which not to.
To warn for DRAW_PIXMAP only you can do this:
DEFINES += QT_DIRECTFB_WARN_ON_RASTERFALLBACKS=DRAW_PIXMAP
To include fillRect you can do:
DEFINES += \"QT_DIRECTFB_WARN_ON_RASTERFALLBACKS=DRAW_PIXMAP|FILL_RECT\"
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
|
| |
All these drawing functions really shouldn't be const even if some of
them can be. They should never be called from const functions and
when/if they change pen/brush stuff they cease being able to be const.
Also make sure fillRegion() uses the right brush.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
|
|
| |
Some PowerVR chipsets are unstable if mmap/PVR2DMemWrap is used to map
screen 0 instead of using PVR2DGetFrameBuffer. This change makes the
driver use PVR2DGetFrameBuffer for screen 0 and mmap/PVR2DMemWrap for
all other screens.
Reviewed-by: Julian de Bhal
|
|
|
|
| |
Reviewed-By: TrustMe
|
|
|
|
|
|
|
|
|
| |
The QIcon::pixmap() call would always load and validate any svg file
that was used for a QIcon, even though there was a cached pixmap
for that particular size.
Task-number: 248848
Reviewed-by: Kim
|