summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMiklos Vajna <vmiklos@collabora.co.uk>2015-08-17 17:10:30 +0200
committerMiklos Vajna <vmiklos@collabora.co.uk>2015-08-17 17:11:44 +0200
commit3c2b80066bf2fba4e7222fb7d30ac7d412539818 (patch)
tree004305da3f0d24c9b358f58504c67e3056ec1a12 /include
parenta19e2064c09275e9b053cc6c13d319c1a5c1c992 (diff)
tdf#93482 vcl rendercontext: add Window::RequestDoubleBuffering()
This allows applications to request enabling/disabling of double-buffering of their VCL frame and all its children. It works after-the-fact, too: so in case the start center creates the frame and later that frame is reused for Writer, then Writer can turn on double-buffering, still. From a user's point of view, this means that next to VCL_DOUBLEBUFFERING_FORCE_ENABLE, there is now also a VCL_DOUBLEBUFFERING_ENABLE environment variable that enables a safe subset that is not supposed to draw directly at all. Enable this for Writer only, for now. Change-Id: Ie2cbf7d467eae2cee37fb58a1efc0a8984204408
Diffstat (limited to 'include')
-rw-r--r--include/vcl/window.hxx2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/vcl/window.hxx b/include/vcl/window.hxx
index a105bddcdc44..57ac3197aaaa 100644
--- a/include/vcl/window.hxx
+++ b/include/vcl/window.hxx
@@ -913,6 +913,8 @@ public:
/// Can the widget derived from this Window do the double-buffering via RenderContext properly?
bool SupportsDoubleBuffering() const;
+ /// Enable/disable double-buffering of the frame window and all its children.
+ void RequestDoubleBuffering(bool bRequest);
void EnableAllResize( bool bEnable = true );