diff options
| author | Luboš Luňák <l.lunak@suse.cz> | 2012-06-22 17:19:12 +0200 |
|---|---|---|
| committer | Luboš Luňák <l.lunak@suse.cz> | 2012-06-22 17:40:09 +0200 |
| commit | ceb8b18f5b7437ba7438c428c3c78e4d8d67fee3 (patch) | |
| tree | d37c8b63df0d31eceabb9976bc0a642699b9e658 /toolkit | |
| parent | 7cb232e6ee80994cf1f8cb17d34e09eb98fdabc7 (diff) | |
use generic names rather than specific algorithm names when scaling
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.
Change-Id: I53765507ecb7ed167890f6dd05e73fe53ffd0231
Diffstat (limited to 'toolkit')
| -rw-r--r-- | toolkit/source/awt/vclxmenu.cxx | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/toolkit/source/awt/vclxmenu.cxx b/toolkit/source/awt/vclxmenu.cxx index c0746a45d9ad..b12d79510ab1 100644 --- a/toolkit/source/awt/vclxmenu.cxx +++ b/toolkit/source/awt/vclxmenu.cxx @@ -678,7 +678,7 @@ namespace sal_Bool bModified( sal_False ); BitmapEx aBitmapEx = aImage.GetBitmapEx(); - bModified = aBitmapEx.Scale( aNewSize, BMP_SCALE_LANCZOS ); + bModified = aBitmapEx.Scale( aNewSize, BMP_SCALE_BEST ); if ( bModified ) aImage = Image( aBitmapEx ); |