|
From: Owen v. D. <owe...@gm...> - 2007-02-06 12:53:29
|
On 2/5/07, Stephan Bezoen <be...@xs...> wrote: > Hi Owen, > As you can see, the function "blur" assumes that only a blur filter will > be applied. It often depends on specific project requirements whether > that's enough (think of stacking of filters), so I think it's a good > idea if you look closely into this and other examples, and get some > skill in writing your own ActionQueue custom functions. With some proper > copy-paste actions you can easily achieve complex effects that apply to > a single project, without necessarily making them very reusable. It > often yields more elegant, understandable and maintainable code than if > you were to use the AQReturnValue or AQProperty functionality. > > The same applies to scrollRect. With a custom function, you can animate > the x- & y-values, and if you wish, the width and height, of a Rectangle > object that is then set as the scrollRect property of a MovieClip. Hi Stephan, Thanks for the reply, I can imagine that a AQScrollRect helper method adds value to asapframework, as it can actually be made reusable ( ie the interface never changes ). I'll be working on a project where tweening filters will be a major part, so i'll see if i can come up with some ideas for a a generic interface. Obviously, stacking filters on top of eachother should be a must-have feature. Maybe a AQFilter helper method that takes a generic filter class and a description how it must handle the tween properties? -- Owen van Dijk |