From 4482f50197f8787f8e187def2cc96758e3c31800 Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Fri, 31 Oct 2014 08:32:31 +0200 Subject: WaE: VarDecl, use "bool" instead of "sal_Bool" [loplugin:salbool] This likely is a false warning or over-enthusiasm in the salbool plug-in, but on the other hand, I don't understand why the recently added case needs to use different coding idioms from the preceding ones in the function? So make the code more uniform. Change-Id: I518022c59f6bd54740676cba95670e78b9a40d19 --- sw/source/uibase/uno/SwXDocumentSettings.cxx | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/sw/source/uibase/uno/SwXDocumentSettings.cxx b/sw/source/uibase/uno/SwXDocumentSettings.cxx index ec71f6dd85e7..b34dd65ec351 100644 --- a/sw/source/uibase/uno/SwXDocumentSettings.cxx +++ b/sw/source/uibase/uno/SwXDocumentSettings.cxx @@ -1248,9 +1248,8 @@ void SwXDocumentSettings::_getSingleValue( const comphelper::PropertyInfo & rInf break; case HANDLE_PROP_LINE_SPACING_SHRINKS_FIRST_LINE: { - sal_Bool const bTmp(mpDoc->getIDocumentSettingAccess().get( - IDocumentSettingAccess::PROP_LINE_SPACING_SHRINKS_FIRST_LINE)); - rValue <<= bTmp; + sal_Bool bTmp = mpDoc->getIDocumentSettingAccess().get( IDocumentSettingAccess::PROP_LINE_SPACING_SHRINKS_FIRST_LINE); + rValue.setValue( &bTmp, ::getBooleanCppuType() ); } break; default: -- cgit v1.2.3