Hi; On Fri, 2007-12-07 at 19:24 +0100, Murray Cumming wrote: > On Fri, 2007-12-07 at 18:17 +0000, Matthew Allum wrote: > > Effects are effectively :) simplified wrappers around behaviours - they > > are easier to use (and nice for 'one shot' transitions etc) but much > > more limited especially when it comes to more complex animations. > > So, I'd use a behaviour instead of an effect when: > - I want it to affect more than one actor > and/or > - I want to start/stop the behaviour and/or change its parameters while > the timeline is running, or even change the alpha-func while the > timeline is running. > - anything else?
Hopefully Ebassi's reply best answers this. > > By the way, the ClutterEffectTemplate object seems to just add > verbosity. It seems like it would be just as easy to supply the timeline > and alpha-callback to each effect function. In fact, that would make it > easier to use different alpha-callbacks if I was, for instance, moving > an actor while fading it. > I guess practically you'll find yourself mixing and matching quite a few effects in one go all needing to be synced. Having the timeline params and alpha in one place (as well as the cloneing flag) makes them all easy to tweak and saves 2 extra args to each effect. == Matthew -- To unsubscribe send a mail to [EMAIL PROTECTED]
