Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hey,

I noticed these lines in file sc/source/core/data/colorscale.cxx
(because cppcheck report indicates that bNeedUpdate is reassigned before to
be used line 641)

    637 void ScDataBarFormat::DataChanged(const ScRange& rRange)
    638 {
    639     bool bNeedUpdate = false;
    640
    641     bNeedUpdate = NeedUpdate(mpFormatData->mpUpperLimit.get());
    642     bNeedUpdate &= NeedUpdate(mpFormatData->mpLowerLimit.get());
    643
    644     bNeedUpdate &= GetRange().Intersects(rRange);
    645
    646     if(bNeedUpdate)
    647     {
    648         mpDoc->RepaintRange(GetRange());
    649     }
    650 }

First I wonder if we shouldn't avoid to bitwise and and logical and. But
above all, shouldn't it be logical OR?

Only for the first one. For the second one the OR is totally wrong and
will force always a repainting which is a preformance nightmare.


So I would rather put:
 if( (NeedUpdate(mpFormatData->mpUpperLimit.get()))
|| (NeedUpdate(mpFormatData->mpLowerLimit.get())) ||
(GetRange().Intersects(rRange)) )
{
    mpDoc->RepaintRange(GetRange());
}

What do you think?

Implemented a correct version with 4f901a2f451a552853c1dd38309dd55b22616fdd.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.