| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Signed-off-by: Thorsten Behrens <tbehrens@suse.com>
|
|
|
|
|
|
|
|
| |
The "faux bold" make the bold font in Asian ugly & unacceptable,
Adjust & improve the "faux bold" to make the bold font better.
Change-Id: I2e02156ffc30629476b80134ffb0b50e793f7ead
Signed-off-by: Jan Holesovsky <kendy@suse.cz>
|
|
|
|
| |
This reverts commit 2f804c94cdaaa9ac047f229509c774dbea1dbcaa.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Lanczos scaling is of very good quality, but it's rather slow,
which can be very noticeable with large images, so it's not a very
good default for everything. And in general, it's not good to refer
to a specific algorithm when all one usually wants is fast/default/best.
Some of these changes are a bit of a guess between default/best,
but the general logic is that best should be used only for images
that won't be large or where the possible waiting does not matter.
Conflicts:
svtools/source/graphic/grfmgr2.cxx
Change-Id: I53765507ecb7ed167890f6dd05e73fe53ffd0231
|
|
|
|
|
|
|
|
|
|
| |
This adds a way to test whether mpCompositeSurface contains the front
buffer image, so it can be used as a source in painting operations.
It means the mpCompositeSurface changed status from 'temporary' to
'persistent' (which it was anyway, from implementation POV :-)
Change-Id: Iee4fc7a97cd60e47d0abb148e7337f0b50cabb40
Signed-off-by: David Tardon <dtardon@redhat.com>
|
|
|
|
|
| |
Change-Id: Icc6f47cc76dfa6716fc44f6c1b5f1b11ba1443c6
Signed-off-by: David Tardon <dtardon@redhat.com>
|
|
|
|
|
| |
Change-Id: Ia0bc37f81b7213b20fc5093beb46d7a05b1ac931
Signed-off-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
|
|
|
|
|
| |
Where we explicitly ask for better quality, use BMP_SCALE_LANCZOS, instead of
BMP_SCALE_INTERPOLATE.
Change-Id: I28ddf3290204532a8660e09ee9ab0949b6ce1c73
|
|
|
|
| |
Change-Id: I73abfa24f5bb7f25afddef820bb4725bf7cee359
|
|
|
|
| |
Change-Id: Id5be3a25fc66d2f7fcec8325491a23d6908021fc
|
|
|
|
| |
Change-Id: I5a254459a491b9547530d8e312260dceed21f25c
|
|
|
|
| |
Change-Id: I43dbe846160d19b203ad6bed06e807d4fbf7ce56
|
| |
|
|
|
|
| |
Change-Id: Idda0262e62e42817b8c0502a38ee16913495233c
|
|
|
|
| |
Change-Id: Idd08fd733670f4410349a45de882710b19a31f67
|
|
|
|
|
|
|
|
| |
this removes dmake completely out of the build for migrated modules
build.pl now assumes modules to be gbuild, unless there is a
prj/dmake file
Change-Id: I674a036b182ee13c5ec093e83cb3d38133112d3b
|
| |
|
| |
|
| |
|
|
|
|
| |
This is to avoid unintended regressions based on configure options.
|
| |
|
|
|
|
|
|
|
| |
Compiles, but I obviously have no idea how it works yet.
Yes, eventually we should factor out common parts from the iOS and
MacOSX code.
|
| |
|
|
|
|
|
| |
- otherwise we might end up with wrong coordinates
- fixes fdo#38580
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
(i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
(i.e. it is registered at the Module, has it's own makefile, may be
in a different module than the target)
|
| |
|
|
|
|
|
|
| |
Pattern used:
find . -name "*.cxx" -exec sed -i 's/\( *\)\(else if\|if\) *( *\([^!()|&]*\)\.equalsAsciiL( *RTL_CONSTASCII_STRINGPARAM *( *\([^)]*\)) *) *)$/\1\2 ( \3 == \4 )/' \{\} \;
|
|
|
|
|
|
| |
Pattern used:
find . -name "*.cxx" -exec sed -i 's/\( *\)return \([^()]*\)\.equalsAsciiL( *RTL_CONSTASCII_STRINGPARAM *( *\([^)]*\) ) *);/\1return \2 == \3;/' \{\} \;
|
| |
|
| |
|
| |
|
|
|
|
|
| |
a13a88bd2c673d059b60e339dcf3b8fabf991f18 changes them to build
without exceptions by mistake, causing a boost problem
|
| |
|
|
|
|
|
| |
White-space changes - code was in parts unreadable after tab/spaces
conversion. While at it, removed a few lines of commented-out code.
|
|
|
|
| |
Did I mention I hate boilerplate copied all over the place? ;)
|
|
|
|
|
| |
vclcanvas has 1bpp alpha - so cut-off transparency at 98%
This looks for all practical cases close enough to full alpha.
|
|
|
|
|
| |
Rather unexpectedly, calling setupOutDevState() with IGNORE_COLOR
does not return a proper transparency, but null. Fixed now.
|
| |
|
|
|
|
| |
This nowadays really is a pessimization.
|
|
|
|
|
| |
Make sure transparent polygons really only cover the polygonal area,
not the whole bounding box for sprites.
|
|
|
|
|
| |
Use GetIndex() instead of GetBlue() (does the same, but more
self-documenting); use opaque when no alpha channel consistently.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...which has the necessary features to support it.
Change a lot of classes to either contain a protected non-virtual dtor
(which is backwards compatible, so even works for cppumaker-generated
UNO headers) or a public virtual one.
cppuhelper/propertysetmixin.hxx still needs to disable the warning, as
the relevant class has a non-virtual dtor but friends, which would still
cause GCC to warn.
Includes a patch for libcmis, intended to be upstreamed.
|
| |
|
| |
|
|
|
|
|
|
| |
With the attachement from said bug, and cairocanvas, sprites
are displayed multiple times above each other (which, for semi-
transparent sprites, lead to incorrect overall transparency)
|