[FusionDev] [compiz] [PATCH] plugin conflict resolution between Fade & Animation

[Erkin Bahceci]

> > On 7/2/07, Sam Spilsbury < smspillaz at gmail.com> wrote:
> > > Could you do that for wobbly too? Also, because you made certain
> animations
> > > of the 'CompTransform' type, could you make them go to the taskbar? I
> think
> > > that there is some code in minimize.c that handles that. Thanks.
> > >
> > > -Sam
> >
> On 7/2/07, Erkin Bahceci <erkinbah at gmail.com > wrote:
> > I was actually going to do the minimization thingy tonight :)
> > And since I converted my Zoom code to CompTransform, now I have that
> > code in Animation plugin as well :)
> >
> > I'll have a look at Wobbly some time, but what is the behavior you
> > want from using Animation and Wobbly together? With the default
> > options there is no conflict here. Does using them together for
> > focus/map effects make sense?
> >
> > Cheers,
> > Erkin
> >
> >
On 7/2/07, Sam Spilsbury <smspillaz at gmail.com> wrote:
> i'm not too sure about wobbly, but I remember that before CCS came along,
> you could load wobbly after animation. I don't know If the plugin load order
> has anything to do with this, but I think that the plugin that is loaded
> beforehand *Hijacks* the animation (And Gridmap) until it is finished,
> leaving the other plugin to finish the animation once the hijacking plugin
> has finished with its gridmap.I think this was the problem.
>
> With a patch like the one fore fade, it may be possible to have wobbly not
> do anything period on minimize/unminimze create/close etc if the shiver
> effect is set to focus. Then on 'actual focus' the wobbly plugin does
> something.

Yeah, that's possible. Delay Wobbly until Animation is done with a
variable/window and a similar event handler in my first fade patch.
But it's a minor and low priority issue, because 99% of current+future
users won't see that conflict because the default settings don't
result in a conflict (even I don't see it on minimize if I try to make
it happen by changing wobbly settings). A patch to fix the wobbly
conflict would require more messing than the other patches I sent. I
don't know if it would get as he didn't even bother commenting on the
patches I sent for the _major_ conflicts that almost everyone will see
if they use animation (and animation will be on by default in most
distributions). So before doing any work on that you might want to ask
David if he would be interested in a patch that solves your problem
(again, I don't have that minimize problem for example). He might be
on vacation or something btw, because he's too quiet these days.

Combining wobbly with animation effects that don't use comptransform
(the 3d polygon-based effects, magic lamp, dream, and the fold
effects) to make them play simultaneously would be a major pain in the
ass, and is simply too much work for a tiny teeny bit of visual
improvement (if any).

> I'm not sure about the utility of map_effect, but there are two ways to
> impliment this :
>
> I think david was speaking about some sort of gridmap interface a while ago
> so that you could have two gridmaps on one window. I'm not too sure about
> this though. Maybe we should nag him?
>
> Also, If we are using comptransform instead of gridmapping (are we?) Then we
> can translate and transform the wobbling window.
>
> Also its great you are now intergrating 'to-taskbar' stuff into the
> animations. Now I can finnally ditch minimize :P