638f6cb6a6
I suppose it is the same misconception as in fdo#55931 - I am convinced that the font metrics should not be used here. Looks to me as if in the past, the font width computation was broken somewhere deep inside OOo, and everyone instead of fixing the root cause was just working that around by using the FontMetric; and then one day the root cause was fixed, and all the workarounds broke ;-) - but that is just a theory. Change-Id: I741bf8f4eaea4f7d8bc698dc9a8124109dfb8c20 |
||
---|---|---|
.. | ||
inc/canvas | ||
prj | ||
source | ||
workben | ||
Library_cairocanvas.mk | ||
Library_canvasfactory.mk | ||
Library_canvastools.mk | ||
Library_directx9canvas.mk | ||
Library_gdipluscanvas.mk | ||
Library_nullcanvas.mk | ||
Library_simplecanvas.mk | ||
Library_vclcanvas.mk | ||
Makefile | ||
Module_canvas.mk | ||
Package_inc.mk | ||
README | ||
StaticLibrary_directxcanvas.mk |
UNO-based graphics backend, lesser impedance to modern graphics APIs than vcl. == The Canvas Framework == The canvas framework is the successor of the system GUI and graphics backend VCL. Basic functionality is available, supplying just as much features as necessary to provide a VCL-equivalent feature set (except proper BiDi/CTL support). The canvas framework consists of the following two modules, canvas and cppcanvas. Additionally, a new generic graphics tooling is used (but not exclusively by the canvas, Armin's drawinglayer module also make use of it), which resides in basegfx. The UNO API used by the canvas is primarily under com::sun::star::rendering, with com::sun::star::rendering::XCanvas being the central interface. == The slideshow engine == The slideshow engine has replaced the former Impress-embedded presentation framework with a fully independent UNO component, and it is based on the canvas. Some features used there are only available from canvas, like double-buffering, and hardware-accelerated alpha-blending (currently not on all platforms).