koffice/krita/image

[Boudewijn Rempt]

On Friday 18 July 2008, Cyrille Berger wrote:
> SVN commit 834389 by berger:
>
> call setDirty after removing a node, this fix redisplay problem after
> removing a node
>
> CCBUG:166388
>
>  M  +2 -0      kis_node.cpp
>
>
> --- trunk/koffice/krita/image/kis_node.cpp #834388:834389
> @@ -265,6 +265,8 @@
>          removedNode->setParent( 0 ); // after calling aboutToRemoveANode
> or then the model get broken according to TT's modeltest
>
>          m_d->nodes.removeAt( index );
> +
> +        setDirty(); // FIXME Would probably better if we could set a QRect

I'm not totally happy about putting a setDirty() here -- one of my goals was 
to remove the amount of calls to setDirty in krita/image so gui code could 
execute any number of actions on the image and then call setDirty on the 
aggregate affected area. I guess I would prefer to call setDirty where layers 
are (re)moved from the gui. But perhaps that's problematical in this case?



-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi