summaryrefslogtreecommitdiff
path: root/sfx2/source
diff options
context:
space:
mode:
authorLuboš Luňák <l.lunak@suse.cz>2012-06-22 17:19:12 +0200
committerLuboš Luňák <l.lunak@suse.cz>2012-06-22 17:38:50 +0200
commit9a6542d6ef25ccaf78ea26e02693a6c0299b3765 (patch)
treea62007979e1371a4f811c72565df6bffda73ab68 /sfx2/source
parent694dd2cf2a109f233df5011d64defcd4254f9975 (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. Conflicts: svtools/source/graphic/grfmgr2.cxx Change-Id: I53765507ecb7ed167890f6dd05e73fe53ffd0231
Diffstat (limited to 'sfx2/source')
-rw-r--r--sfx2/source/toolbox/tbxitem.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/sfx2/source/toolbox/tbxitem.cxx b/sfx2/source/toolbox/tbxitem.cxx
index d220e71c7770..3573f4b11c52 100644
--- a/sfx2/source/toolbox/tbxitem.cxx
+++ b/sfx2/source/toolbox/tbxitem.cxx
@@ -1550,7 +1550,7 @@ void SfxAppToolBoxControl_Impl::SetImage( const String &rURL )
if ( bBig && aImage.GetSizePixel() != aBigSize )
{
BitmapEx aScaleBmpEx( aImage.GetBitmapEx() );
- aScaleBmpEx.Scale( aBigSize, BMP_SCALE_LANCZOS );
+ aScaleBmpEx.Scale( aBigSize, BMP_SCALE_BEST );
GetToolBox().SetItemImage( GetId(), Image( aScaleBmpEx ) );
}
else