Flash printing in SWF error in Flash CS3.
Not sure if anyone else has seen this before but, one of the designers at work was trying to use PrintJob() and for some reason the printed page was showing with a blue tint. I thought it was odd, so I gave it a crack. Sure enough, blue hue on everything. Even when I tried to use print() I would get the same blue freakin hue.
We spent a lot of time looking at it, but found out that when we looked at the swf outside of the Flash IDE the blue went away. So word to the wise, if you get the error just try it outside of the Flash IDE.
We spent a lot of time looking at it, but found out that when we looked at the swf outside of the Flash IDE the blue went away. So word to the wise, if you get the error just try it outside of the Flash IDE.
Labels: Flash
2 Comments:
Just ran into the same damn thing today.
Came to the conclusion a few minutes ago after killing about 2 hours on it before a buddy pointed me to your post. what a pain.
I can't believe the troubles I was having with this issue, either. There seemed to be no logical explanation, since everything was printing perfectly fine yesterday afternoon... Came out perfectly fine on MAC OS/X until I tested it from Windows later that night, and I discovered the black box surrounding the PNG background. A bit of research found that I needed to have the PrintJobOption's "printAsBitmap" property set for alpha/colour-effects to be printed properly... lo and behold, the prints worked perfectly fine again.
Then earlier this morning, I'm back here at work (on Mac) and telling my boss about how I'd solved the problem... only to uncover another one, this time being the accursed blue background (that we weren't having yesterday, for some reason). We'd all been doing our testing offline, rather than online... and it's still having the same issue when printing from Flash's offline Flash Player. Online, however, it prints perfectly bloody fine...
*shrugs* Beats me, but I spent ages surfing around on Google before this blog gave me an answer... thank you for this. =) Good to know I'm not the only one having this issue; Adobe need to get off their arses and get this annoying little bug sorted out...
Post a Comment
<< Home