Compiz wobbly.c

[Stuart Kreitman]

Ahmed:

I see the purpose of this patch, but would inquire whether 
damagePendingOnScreen() is
invoked more than necessary and what impact that would have on performance.

 From the supplied diff,  I can see one questionable case, cut out 
below. In general, is there a more
common exit point that might get the job done in one call for more code 
paths?

Ahmed Ammar wrote:

> 		    if (ww->grabbed && ww->model)
> 		    {
>+			damagePendingOnScreen (w->screen); //aa
> 			if (modelDisableSnapping (w, ww->model))
> 			{
> 			    ww->wobbly |= WobblyInitial;
> 			    ws->wobblyWindows |= ww->wobbly;
> 
>-			    damagePendingOnScreen (w->screen);
>+			   damagePendingOnScreen (w->screen);   <=======HERE
> 			}
> 		    }
> 		}
>
>
>  
>