summaryrefslogtreecommitdiffstats
path: root/src/gui/embedded/directfb.pri
diff options
context:
space:
mode:
authorAnders Bakken <anders.bakken@nokia.com>2009-08-28 03:37:40 (GMT)
committerAnders Bakken <anders.bakken@nokia.com>2009-09-01 22:25:51 (GMT)
commitadd57539ec7cd24346e26b22a5298da50d81e91b (patch)
treefda78f056d25bd876b7348bf732463939b9fe648 /src/gui/embedded/directfb.pri
parent913a21aae513714217be233c6cecfb39212a4be8 (diff)
downloadQt-add57539ec7cd24346e26b22a5298da50d81e91b.zip
Qt-add57539ec7cd24346e26b22a5298da50d81e91b.tar.gz
Qt-add57539ec7cd24346e26b22a5298da50d81e91b.tar.bz2
Rewrite of DirectFB locking mechanism
DirectFB allows you to have a locked subSurface that remains valid while you paint on the unlocked "parent" surface. The only limitation is that when accessing the locked memory you might have to call DirectFB->WaitIdle() in case pending GPU operations aren't finished. After this we keep the locked surface around at all times (from the first time it's requested) until the surface dies. Previous calls to lock() will just call WaitIdle if necessary and previous calls to unlock now just mark the surface as dirty and in need of a WaitIdle if someone needs to access its pixel data. Reviewed-by: Donald Carr <donald.carr@nokia.com>
Diffstat (limited to 'src/gui/embedded/directfb.pri')
-rw-r--r--src/gui/embedded/directfb.pri1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/gui/embedded/directfb.pri b/src/gui/embedded/directfb.pri
index e868252..7dae9d5 100644
--- a/src/gui/embedded/directfb.pri
+++ b/src/gui/embedded/directfb.pri
@@ -1,6 +1,7 @@
# These defines might be necessary if your DirectFB driver doesn't
# support all of the DirectFB API.
#
+#DEFINES += QT_NO_DIRECTFB_SUBSURFACE
#DEFINES += QT_DIRECTFB_WINDOW_AS_CURSOR
#DEFINES += QT_NO_DIRECTFB_IMAGEPROVIDER
#DEFINES += QT_DIRECTFB_IMAGEPROVIDER_KEEPALIVE