mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vcl: document what LO_COLLECT_UIINFO does and how to use it

Browse Source 
See <https://wiki.documentfoundation.org/Development/UITests> for more
info.

Change-Id: I17f647a5c67aa6aef3bf7ac4743fdc778f8a59d3
Reviewed-on: https://gerrit.libreoffice.org/78836
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Tested-by: Jenkins
This commit is contained in:
Miklos Vajna 2019-09-12 17:20:31 +02:00
parent 166dc8778d
commit 7dfc3d2def
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
vcl/README.vars
View File

@ -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)