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? 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. > > == Matthew > > On Fri, 2007-12-07 at 18:59 +0100, Murray Cumming wrote: > > > On Fri, 2007-12-07 at 14:16 +0000, Matthew Allum wrote: > > > > - I would explain effects before behaviours. They are much easier to > > > > grasp. > > > > I hadn't noticed them before. > > > > So, what's the advantage of using a behaviour over using an effect? Both > > change specific properties via a supplied alpha callback while a > > timeline runs. I can see that a behaviour can be applied to multiple > > actors, but is that the only difference? > > > > -- > > [EMAIL PROTECTED] > > www.murrayc.com > > www.openismus.com > > > -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com -- To unsubscribe send a mail to [EMAIL PROTECTED]
