summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src_gui_kernel_qkeysequence.cpp
diff options
context:
space:
mode:
authorJason Barron <jbarron@trolltech.com>2010-02-04 13:15:56 (GMT)
committerJason McDonald <jason.mcdonald@nokia.com>2010-02-09 16:20:32 (GMT)
commit9cd2b2b052b13839c700b17b3baa61ef9981c3d3 (patch)
treee5bc124803f78d1ccc4b9408cec214eb61510529 /doc/src/snippets/code/src_gui_kernel_qkeysequence.cpp
parenta904af2eaf9ab1290730ae76bfa59c3768ff0ebe (diff)
downloadQt-9cd2b2b052b13839c700b17b3baa61ef9981c3d3.zip
Qt-9cd2b2b052b13839c700b17b3baa61ef9981c3d3.tar.gz
Qt-9cd2b2b052b13839c700b17b3baa61ef9981c3d3.tar.bz2
Flush the WSERV command buffer after deleting a surface.
For graphics systems that use EGL surfaces in the backing store destroying the surface does not guarantee that the memory is immediately freed because this command does not cause a flush. This implies that a manual flush is instead needed. We do this in 2 places; the first is when the surface is destroyed due to a visibility changed. The second case is just after the window has been destroyed. At this point the backing store has already been deleted so the deletion of both the surface and window can happen atomically in WSERV. Task-number: QT-2506 Reviewed-by: Iain (cherry picked from commit 91e236022acd79dfbc4aef9e30edb4d1aeb2685c)
Diffstat (limited to 'doc/src/snippets/code/src_gui_kernel_qkeysequence.cpp')
0 files changed, 0 insertions, 0 deletions