Comments on: Flex Move Effect Messes Up Mask Alignment

By: Use cacheAsBitmap correctly - or not at all « Bagonca

Use cacheAsBitmap correctly - or not at all « Bagonca — Fri, 17 Apr 2009 15:04:01 +0000

[…] Why cacheAsBitmap is bad Flex Move Effect Messes Up Mask Alignment […]

By: Jon

Jon — Fri, 17 Apr 2009 14:50:43 +0000

Also, did you try UIComponent.cachePolicy = UIComponentCachePolicy.OFF since default is
UIComponentCachePolicy.AUTO which basically means that the FlashPlayer will heuristically try and figure out whether you usually cacheAsBitmap. From what I can see in Flex 3, this may be what resulted in the default to cache = true in your case.

By: Jon

Jon — Fri, 17 Apr 2009 14:37:32 +0000

I came across a similar problem myself when for some reason ivoking cacheAsBitmap on flexlibs DragScrollingCanvas (somebody else must have checked that code in…). Everything was hunky dory on a PC but on Mac the whole view got corrupted after the user had scrolled around for a bit.

As it happens I was also working on an implementation of a timeline.

By: Zarate

Zarate — Thu, 20 Nov 2008 18:46:15 +0000

"You just need to understand the Flex SDK. I clearly donâ€t;" I thought I was the only one : )

By: JesterXL

JesterXL — Thu, 20 Nov 2008 16:12:36 +0000

I did some more investigation as the problem popped up again, and it’s attempting to set cacheAsBitmap to true inside the framework itself. Merely resetting the mask in actuality didn’t help. So, I ended up overriding UIComponent’s cacheAsBitmap setter to force it to be always false. That seemed to do the trick.