mirror of
https://github.com/LibreOffice/core.git
synced 2025-07-26 15:45:26 +00:00
7c483a0d52
A PixelSnap was used before using GetOutputDevice() and LogicToPixel/PixelToLogic (what was incorrect, would need to take care of 1/2 pixel in logic for rounding). We do not need that anymore, in fact it leads to the text slightly 'jumping' around by up to 1 pixel (of course). We paint text nowadays using decomposed TextPrimitives with sub-pixel precision and similar (using a shortcut) for text in TextEdit on the Overlay, also using sub-pixel precision. Just remove this to avoid Text being displayed different in TextEdit and EditView paint visualizations and assign given value to OutputArea unchanged. If this should cause problems somewhere (I do not think so, we try to paint text with Sub-Pixel quality now anyways) this can also be done in alternative ways and only for TextEdit on Overlay. Change-Id: If177ceec880a29a6d102ad4f0dddf891d95b69c2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/182094 Tested-by: Jenkins Reviewed-by: Thorsten Behrens <thorsten.behrens@allotropia.de>
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"