http://bugs.opencompositing.org/show_bug.cgi?id=1109
--- Comment #7 from SmSpillaz <smspil...@gmail.com> 2009-01-25 01:31:56 --- (In reply to comment #3) > (In reply to comment #1) > > No it's the fade plugin that does the animation. You can change the speed in > > the plugin's options page, 'Fade Speed'. > > That's wrong. Fade doesn't do any animation of obs' > opacity/brightness/saturation changes. obs wraps into drawWindow, fade has no > chance of picking up those changes. Ah right, I thought that it would have only made sense for obs to wrap into paintWindow and have the fade plugin to apply it's changes from there. > > > Idealistically though, we really need to drop Fade and think of a better > > solution. Fade is quite a weird hack that depends on how the old compiz > > wrappable system worked. It definitely wouldn't work with compiz++. > > That's wrong. Compiz++' opengl plugin has GLWindow::glPaint and > GLWindow::glDraw, which are the exact equivalent of compiz' paintWindow and > drawWindow routines. As far as I can see, fade will continue to work just fine > with compiz++ (after it has been ported, obviously). > Really? I thought compiz++ didn't make use of a call chain anymore? Anyways, the method fade uses is not exactly the best as it only allows for one fade speed. I think we should talk to david about the animation timeline framework and making fade a library plugin (FadeInterface?) for animating windows properly. -- Configure bugmail: http://bugs.opencompositing.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Dev mailing list Dev@lists.compiz-fusion.org http://lists.compiz-fusion.org/mailman/listinfo/dev
