This content has been marked as final. Show 3 replies
The problem is sandbox and URL confusion on the part of AIR when SWF content is loaded in HTML. You can load the secondary files in this situation with an absolute path or a remote URL, but not using a relative path.
As a work around, you can load the videoplayer in an sandboxed iframe, such as:
<iframe src=" http://foo.com/videoplay.htm" width="100%" height="100%"
sandboxroot=" http://foo.com" documentroot="app:/foo"></iframe>
where the videoplayer is loaded by foo/videoplay.htm and the player, movies and skins are in the foo directory.
You might also be able to open a video player window using a file:/// URL, which should achieve the same end.
Thanks Joe. I'm using the file:// method for this and I have the vidoes playing. I'm working on some cross-platform issues in determining the proper path, but I think I can get through those.