If you’ve written at least once the OBJECT and EMBED tags, without copy/paste you may have been noticed that the place of the EMBED tag is a bit strange. Actually after the OBJECT tag, comes the PARAM sequence, that simply defines different parameters for the flash movie.
And what looks strange?
The strange thing in all this is that the EMBED tag, which in fact is only one, instead of the case with all the parameters of the OBJECT, is displayed just before the closing of the OJBECT tag.
Experimenting …
What if the embed tag is outside of the OBJECT opening and closing tags. Actually only IE understands this as a problem. Than it displays the move twice!
That’s why the place of the EMBED is just before closing the OBJECT tag. In that case MSIE doesn’t “see” the EMBED and displays everything correctly!
If someone wanders why the fullscreen doesn’t work correctly under IE, after calling StageDisplayState.FULL_SCREEN in Flex – there’s the answer. Just don’t forget to add
<param name=”allowFullScreen” value=”true”>
parameter of the object tag. You may also set allowFullScreen=”true” of embed tag.
If you’d like to embed a .swf file into your Flex 3 application you’ll probably get into several little problems. The simple task of embedding is clear and well documented in the web. Let’s assume we’ve to MovieClip symbols into a single .swf file. What we like to do is to access this two separate symbols within the Flex applications as MovieClip.
Make the .swf sample file with both symbols inside. In general it’s not that hard, just put this into your Flex application code:
[Embed(source="embed.swf", symbol="blue")]
private var blue:Class;
[Embed(source=”embed.swf, symbol=”red”)]
private var red:Class
Note that you’ve embed.swf file, which has to be in the same folder as the main .swf of the Flex app, and two symbols named red and blue for the sample. Be very careful when exporting the symbols from the .swf file. Do not forget to export them for actionscript.
If not exported like that, you’ll have trouble accessing them from the Flex app, and that’s the first problem you can have here.
The rest you have to do is to add this two lines of code in Flex:
var mc:MovieClip = new blue();
this.addChild(mc);
Note that the last line can have something else than ‘this’ if there’s other element to become parent of the imported MovieClip symbol. Here comes the first major problem. As www.airtightinteractive.com describes this technique does not work every time:
Sometimes when you do this you will get the following error:
TypeError: Error #1034: Type Coercion failed: cannot convert app_red@12510d1 to flash.display.MovieClip.
And the author shares his solution which is to add at least 2 keyframes for both movie clips, so that they can be visible as movie clips, if not they will remain visible only as Sprites.
I’m not as conviced this is the right answer of the question and the right solution. I’ve experimented with 1 or 2 keyframes and still have the same problem in Flex even if i cast the symbols as Sprite, not MovieClip:
var mc:MovieClip = new blue();
var mc:Sprite = new blue();
The solution from Adobes for me is not suficient, cause the movie clips we import (embed) does not serve as images but more like movie clips, which was the task from the beggining. And that’s what Adobe says:
Flex fully supports embedding Flash SWF files. You can embed different types of SWF files. … To reference a symbol, you specify the symbol parameter: [Embed(source=’SWFFileName.swf’, symbol=’symbolName’)]
And again read carefully the note in the Adobe’s site:
Note: Flash defines three types of
symbols: Button, MovieClip, and Graphic. You can embed Button and
MovieClip symbols in a Flex application, but you cannot embed a Graphic symbol because it cannot be exported for ActionScript.
Here you can be sure that lack of exported for actionscript symbol is not accessible in Flex.
One of the main solutions is to embed the .swf as octet-stream:
[Embed(source="embed.swf", mimeType="application/octet-stream")]
private var blue:Class;
followed by:
var loader:Loader = new Loader()
loader.loadBytes(new blue());
And the key point of this will be the lines:
var red:Class = loader.contentLoaderInfo.applicationDomain.getDefinition("blue");
var mc:MovieClip = new red() as MovieClip;