local3DToGlobal and Matrix3D shennanigans!

Just spent a few hours debugging this little delightful side effect of using local3DToGlobal on a DisplayObject that I’d set it’s matrix3D property to null (to remove the effect of blurry graphics after 2.5D rotations and z translations).

Beware: using local3DToGlobal on a DisplayObject that doesn’t have a matrix3D property will result in that DisplayObject having a new matrix3D property created on it’s behalf. Not sure that’s entirely logical, but it’s what the boffins at Adobe thought was best… grrrrrrrr!

Be Sociable, Share!
Posted in Actionscript, Flash

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Posts this month
February 2012
M T W T F S S
« Nov   Jun »
 12345
6789101112
13141516171819
20212223242526
272829  
Archives