office-gobmx/editeng
Patrick Luby ccc31ed4d9 tdf#156470 add SAL_INFO calls for debugging
In the verious LibreOffice samples attached to tdf#156470, it appears
that LibreOffice spends a lot of time the GetTextArray() calls in
SvxFont::QuickGetTextSize(). So add logging to determine if any of
the GetTextArray() calls are returning unusual sizes.

Change-Id: Ie6f0fcc85396b47342b6a93180d4bc9873420931
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155072
Tested-by: Jenkins
Reviewed-by: Patrick Luby <plubius@neooffice.org>
2023-07-31 18:11:53 +02:00
..
inc
qa
source tdf#156470 add SAL_INFO calls for debugging 2023-07-31 18:11:53 +02:00
uiconfig/ui
AllLangMoTarget_editeng.mk
CppunitTest_editeng_borderline.mk
CppunitTest_editeng_core.mk
CppunitTest_editeng_lookuptree.mk
CustomTarget_generated.mk
IwyuFilter_editeng.yaml
Library_editeng.mk
Makefile
Module_editeng.mk
README.md
UIConfig_editeng.mk

Edit Engine

In OpenOffice.org build DEV300m72 this module was split off from svx but it has no dependencies on svx (nor on sfx2) while in turn svx depends on editeng

Read more in the mailing list post: http://www.mail-archive.com/dev@openoffice.org/msg13237.html

If you build LibreOffice with dbgutil, you have some extended debug keys:

  • Ctrl+Alt+F1 - draws the paragraph rectangles in different colors
  • Ctrl+Alt+F11 - toggles dumping the edit engine state to the "editenginedump.log" on draw
  • Ctrl+Alt+F12 - dumps the current edit engine state to "editenginedump.log"