Can you provide a sample project that recreates your issue? I'll be happy to see if 4.6 and 4.7 behave differently (with the same AIR 3.5 1066) both locally and on an iPad. PM me a link if you don't want to share it publicly.

I would file it as an Adobe Flash Player v11.5 bug that all users will encounter that's of type `Incorrectly functioning w/ workaround`. Attach the file you shared above and mention the code-based workaround.

I followed your suggestion, and filed it as FlashPlayer 11.5 bug w. workaround. In retrospect, I regret the last, as the bug

was positioned as only as "priority 3rd high" - presumably because of the existence of the theoretical workaround.

For me, the work around is not realistic, because I use these filters at hundreds of places. Finding, then removing them,

and adding them programmatically would be an adminstrative nightmare, and I'd loose the WYSIWYG advantage of Flash Pro completely.Summarized - until fixed, I cannot use FB4.7. to continue the development of my app in.

Anyway, I'll keep my fingers crossed that the "FlashPlayer bug" will make it to the FlasBuilder team (in some coorperations I've worked,there'd be high chances such "ill-filled in form" would be ignored) - and that they'll give it high priority, which I think it deserves.

I wish it was more prompt but I lost power and net for days in that US blizzard over the weekend. Whew, happy to be back.

Please post your bug report ID here so we can vote on the issue. The number of people voting on it is what largely controls the speed it is fixed. Also go in the Flash Builder forum and post the bug link there.

As for the workaround, their nature is definitely to be annoying. They're not ideal. FB "just working" is the best solution by far but a known workaround for someone else who doesn't have thousands of filters might make or break their deadline. It also gives valuable clues to the patching team on where the problem may lie. I'd always include a workaround if you find one.

Mmm.. looks like bureaucracy prevents the bug to be considered (see bugbase link above).Zhe Wang, a Lead Manager of Adobe seems to have rejected the bug-report, because"it should be filed as an FB bug instead of a FlashPlayer Bug".

Apparently, there's no way to report a bug to the FB team. I can't hide that its

Thank you for hinting this other potential workaround. I'll see if I can reproduce.

This workaround would mean that each of the exported main classes in flash pro would need to be dissected hard-coded into sub-classes in the code, at least for each sub-class (movieclip) that uses such a filter - hard code an extended class for these classes, and then rebuild an analogon of the original main class at runtime that uses these extended classes to in a similar hierarchical buildup.

That is, even if the workaround would work, it'd still cost tons of work for me

Indeed, your project, using flex/mx/spark does show the pink of the button that is contained in the swc properly.

That's good. On the first sight, it looks like FB47 can be used using these addons. Many thanks.(I'll need to figure out how to if it does not come at the price of additional memory usage, and if subsequential builds forios and android are without problems. - yet if the answers of these questions are positive - you surely have saved me - anyway - many thanks!!)

Retrying as as3 project still does not work.

From our exchange above, I'm not 100% certain: Have you succesfully tested with normal as3 projects as well?

(The question is, if something triggered a "fix" at your system, or that that did not happen, or and our results arein sync now)