From 7dfc3d2def531fcdcfbf27f68c384fded1a948a1 Mon Sep 17 00:00:00 2001 From: Miklos Vajna Date: Thu, 12 Sep 2019 17:20:31 +0200 Subject: [PATCH] vcl: document what LO_COLLECT_UIINFO does and how to use it See for more info. Change-Id: I17f647a5c67aa6aef3bf7ac4743fdc778f8a59d3 Reviewed-on: https://gerrit.libreoffice.org/78836 Reviewed-by: Miklos Vajna Tested-by: Jenkins --- vcl/README.vars | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vcl/README.vars b/vcl/README.vars index b170bb22c027..0530195363d8 100644 --- a/vcl/README.vars +++ b/vcl/README.vars @@ -10,6 +10,9 @@ SAL_FORCE_HC - force high-contrast mode SAL_NO_FONT_LOOKUP - disable font search and fallback and always use a hard-coded font name (for some unit tests) +LO_COLLECT_UIINFO - enable the uitesting logging, value is expected to be a relative file name that +will be used to write the log under instdir/uitest/. + VCL_DOUBLEBUFFERING_AVOID_PAINT - don't paint the buffer, useful to see where we do direct painting VCL_DOUBLEBUFFERING_FORCE_ENABLE - enable double buffered painting VCL_DOUBLEBUFFERING_ENABLE - enable a safe subset of double buffered painting (currently in Writer, not in any other applications)