search

freem-trg / eaze-tween

Automatically exported from code.google.com/p/eaze-tween
0 stars 0 forks source link

When using blur filter the filter applies 4 on blurX and blurY #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
This will add a blur blurY = 4.
eaze(this)
.to(.5, { blurFilter:{ blurX:5 } } );

I think it would be more easy to use if it starts with BlurFilter( 0, 0, 1
); otherwise the filter will automagicly add blurY = 4, even if only want
to tween the blurX property.

What version of the product are you using? On what operating system?
beta5 r65

Original issue reported on code.google.com by jakobste...@gmail.com on 19 Jan 2010 at 12:19

GoogleCodeExporter commented 9 years ago 
blurY=4 is the filter default value as seen in AS3 langref:
http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/filters/BlurFilt
er.html

Original comment by philippe...@gmail.com on 19 Jan 2010 at 2:58

GoogleCodeExporter commented 9 years ago 
That's my point why should the default value be set, if I'm planning to use the
property anyway, I think it should be set to 0 and optional to add a value. 
From my
point of view it's just a mistake from Adobe, having optional values in 
constructor
that I'm not planning to use. 

eaze(this)
.apply( { blurFilter:{ blurX:0, blurY:0 } } )
.to( .5, { blurFilter:{ blurX: 10 } );

Anyway thanks for a kickass syntax!

Original comment by jakobste...@gmail.com on 19 Jan 2010 at 3:20

GoogleCodeExporter commented 9 years ago 
Eaze does not set anything: a new BlurFilter is created (and receive its 
default 
values), then your custom values are applied.

But maybe you're right and it would be more natural to initialize the objects 
with more 
appropriate defaults than filter classes defaults.

Original comment by philippe...@gmail.com on 19 Jan 2010 at 3:25