summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src_gui_embedded_qscreen_qws.cpp
diff options
context:
space:
mode:
authorGunnar Sletta <gunnar@trolltech.com>2009-04-23 07:16:53 (GMT)
committerGunnar Sletta <gunnar@trolltech.com>2009-04-24 08:47:39 (GMT)
commit861651c67a5f627f615ac1542f945e3c11593406 (patch)
tree35d4d9a9d9343ddf4751fd1b51931f491c8a58f2 /doc/src/snippets/code/src_gui_embedded_qscreen_qws.cpp
parent89aa644baabd8a118a59cb367aca2adf1363564e (diff)
downloadQt-861651c67a5f627f615ac1542f945e3c11593406.zip
Qt-861651c67a5f627f615ac1542f945e3c11593406.tar.gz
Qt-861651c67a5f627f615ac1542f945e3c11593406.tar.bz2
Implement QRasterPaintEngine::clip(QRegion) to do something sensible...
Since we now store QRegion's in the clipdata is possible for us to detect that we should go back to a rect-clip mode when we get to clip(region) or clip(rect) It turns out that the qt_span_fill_clipRegion is very slow, even for smaller regions, testcase was 3 rects, its 10% worse than span based clipping. For a fullscreen ellipse it was more in the range of 100x worse, so I removed the clip function entirely.
Diffstat (limited to 'doc/src/snippets/code/src_gui_embedded_qscreen_qws.cpp')
0 files changed, 0 insertions, 0 deletions