summaryrefslogtreecommitdiffstats
path: root/src/plugins/gfxdrivers/directfb/qdirectfbscreen.h
diff options
context:
space:
mode:
authorAnders Bakken <anders.bakken@nokia.com>2009-04-28 03:36:29 (GMT)
committerAnders Bakken <anders.bakken@nokia.com>2009-04-28 20:12:05 (GMT)
commit2e9071afbf86ca3143552a3eed75418328b5ce6c (patch)
tree37e15cca39c2fc9b32de956306d9b31956210a65 /src/plugins/gfxdrivers/directfb/qdirectfbscreen.h
parentde14db188ada5e00980a152dadb13d38438a7fa2 (diff)
downloadQt-2e9071afbf86ca3143552a3eed75418328b5ce6c.zip
Qt-2e9071afbf86ca3143552a3eed75418328b5ce6c.tar.gz
Qt-2e9071afbf86ca3143552a3eed75418328b5ce6c.tar.bz2
Added an option for ignoring the system clip
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>
Diffstat (limited to 'src/plugins/gfxdrivers/directfb/qdirectfbscreen.h')
-rw-r--r--src/plugins/gfxdrivers/directfb/qdirectfbscreen.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/plugins/gfxdrivers/directfb/qdirectfbscreen.h b/src/plugins/gfxdrivers/directfb/qdirectfbscreen.h
index 8dd38dc..08c9ac1 100644
--- a/src/plugins/gfxdrivers/directfb/qdirectfbscreen.h
+++ b/src/plugins/gfxdrivers/directfb/qdirectfbscreen.h
@@ -109,6 +109,7 @@ public:
void releaseDFBSurface(IDirectFBSurface* surface);
bool preferVideoOnly() const;
+ bool ignoreSystemClip() const;
static int depth(DFBSurfacePixelFormat format);