fourBoxWipe, ellipseWipe, pinWheelWipe). Basic support for reverse
method by subtraction.
Ported or implemented the following classes or functions:
createShapeTransition, ClippingAnimation.
Extended the following SVG DOM classes: SVGPathElement (prependPath
method).
Modified and added new methods to: AnimatedElement, ClippingFunctor,
EllipseWipePath, FourBoxWipePath.
fourBoxWipe, ellipseWipe, pinWheelWipe).
Ported or implemented the following classes or functions:
ClippedSlideChange, PathTools.normalizePath, ClippingFunctor,
createClipPolyPolygon, BarWipePath, FourBoxWipePath,
PathTools.createPathFromEllipse, EllipseWipePath, PinWheelWipePath.
Extended the following SVG DOM classes: SVGMatrix, SVGPathElement,
SVGPathSegMovetoAbs, SVGPathSegLinetoAbs, SVGPathSegCurvetoQuadraticAbs,
SVGPathSegCurvetoCubicAbs.
Modified and added new methods to: MetaDocument, AnimatedSlide,
SlideTransition, TransitionInfoTable.
Ported or implemented the following classes: SlideTransition,
AnimatedSlide, SlideChangeBase, FadingSlideChange,
FadingOverColorSlideChange, MovingSlideChange.
Modified and added new methods to: MetaSlide, SlideShow.
to
modify the part of the presentation engine handling the slides
navigation feature.
A new structure for slide and master page elements has been designed.
The following new classes have been implemented: MasterPageView,
TextFieldHandler, SlideNumberFieldHandler.
The following classes have been modified: MetaDocument, MetaSlide,
MasterPage, PlaceholderShape, Thumbnail.
The following classes have been modified and renamed: TextField ->
TextFieldContentProvider, FixedTextField -> FixedTextProvider,
VariableDateTimeField -> CurrentDateTimeProvider, SlideNumberField ->
SlideNumberProvider.
These RID definitions aren't used at any other point. So remove
them. Unused START and END definitions were commented out for
documentation purpose.
All definitions in basctl/source/basicide/tbxctl.hrc were unused,
so I removed this file.
Change-Id: I4713188a12b9da912b2a91b85ea4e54ca1aeb994
I could not use boost::ptr_vector because some of the code copies
the pointers into other data-structures temporarily, which
ptr_vector does not like.
Change-Id: Ie9c8aeb4e741bfd138694929ccda451a1c0984bb
I could have used boost::ptr_vector, but the code seems to believe
that the array can contain nulls, which ptr_vector does not like.
Change-Id: I5f56a3e96ef9baca2c192e7cfa33b8f4283709a6
Update code to use factory method URLTransformer::create
Change-Id: I3fd2e838497bcfd8fc949615c0e7d60a6ea47118
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>, added some tweaks.
Update code to use factory method PathSubstitutions::create
Change-Id: I3721bd93c36b207d849eea19102f5ac61cadd205
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>, added some tweaks.
Where we explicitly ask for better quality, use BMP_SCALE_LANCZOS, instead of
BMP_SCALE_INTERPOLATE.
Change-Id: I28ddf3290204532a8660e09ee9ab0949b6ce1c73
MSO uses undocumented properties that seem to map to o:hr and o:hrpct
from .docx (including differences between .docx spec and implementation),
so treat horizontal rule width the same way in .doc too. Also remove
the guesswork for #i17200# that is not quite correct and no longer needed.
Change-Id: Ibec543fa1679ca0b20e86ef6b4f77147b18dff7e
This way we can run detection services in the correct order; from
more complex to less complex, since the more complex structure is
much easier to test and reject.
Change-Id: Iee2d3e2e4f2834f95e6e89975f646e3928114b11
