SWFLoader Bugs?!!!!!!!!!!!!!

I am trying to do the communication betwen Flex with Flash (SWF) loaded by SWFLoader. However, I always encounter the problem that sometimes the program do run properly, but sometime it doesn't even start up.
Here is my Flex code:
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                            xmlns:s="library://ns.adobe.com/flex/spark"
                            xmlns:mx="library://ns.adobe.com/flex/mx">
     <s:layout>
          <s:VerticalLayout/>
     </s:layout>
     <fx:Script>
          <![CDATA[
               [Bindable]
               protected var flashSaid:String = "";
               protected var mySwfMc:MovieClip;
               protected function setSwfMc():void{
                    mySWFLoader.content['myFlexParent'] = this;
                    mySwfMc = mySWFLoader.content as MovieClip;
               public function listenToFlash(stringToShow:String):void{
                    flashSaid = stringToShow;
               protected function talkToFlash(stringToPass:String):void{
                    mySwfMc.listenToFlex(stringToPass);
          ]]>
     </fx:Script>
     <fx:Declarations>
          
     </fx:Declarations>
     <mx:SWFLoader id="mySWFLoader" source="talk.swf" complete="setSwfMc()"/>
     <s:Button label="sendtoFlash" click="talkToFlash('hehehhhe')"/>
     <s:Label id="distxt" text="{flashSaid}"/>
</s:WindowedApplication>
Here if my Flash Code (created using Flash CS3, setting: AS3, Flash Player 9):
var myFlexParent:Object;
var i:Number;
function talkToFlex(me:MouseEvent):void{
     myFlexParent.listenToFlash("heheheheheeh");
function listenToFlex(stringToShow:String):void{
     flexSaidTxt.text = stringToShow;
talkToFlexBtn.addEventListener(MouseEvent.CLICK,talkToFlex);
I have tried to fixing and make the thing works for almost 2 days, but it didn't. The weird thing is that, I have tried to remove the script code, everything except the swfloader to load the swf file, the application window appears when I try to run the application, but the component inside it jumping up and down crazily.
The console window shows me:
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
[SWF] talk.swf - 2,684,356 bytes after decompression
Do you know why is this happens? How can I solve it? Thanks.

Thanks for your reply. Curiously, I have checked the talk.swf file. The file size is only 20KB and Flex is loading the correct file. Don't know why Flex sees it as 2MB?
Basically, do you see any error in the code?

Similar Messages

SWFLoader bug

Hello,
First, we will make a simple SWF file that displays a bar
chart; here is the mxml:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute"
applicationComplete="initApp()">
<mx:Box id="supDoc" width="100%" height="100%">
<mx:ColumnChart id="myChart" width="100%"
height="100%"/>
</mx:Box>
</mx:Application>
Then, if you try to load this SWF ONCE using SWFLoader in
actionscript, you will encounter no problems. However, if you try
to load it TWICE, you will get the following error:
TypeError: Error #1034: Type Coercion failed: cannot convert
mx.graphics::Stroke@3e66a41 to mx.graphics.IStroke.
at mx.charts::AxisRenderer/mx.charts:AxisRenderer::measure()
at
mx.core::UIComponent/mx.core:UIComponent::measureSizes()[C:\dev\GMC\sdk\frameworks\mx\cor e\UIComponent.as:5360]
at
mx.core::UIComponent/validateSize()[C:\dev\GMC\sdk\frameworks\mx\core\UIComponent.as:5306 ]
at
mx.managers::LayoutManager/mx.managers:LayoutManager::validateSize()[C:\dev\GMC\sdk\frame works\mx\managers\LayoutManager.as:554]
at
mx.managers::LayoutManager/mx.managers:LayoutManager::doPhasedInstantiation()[C:\dev\GMC\ sdk\frameworks\mx\managers\LayoutManager.as:637]
at Function/
http://adobe.com/AS3/2006/builtin::apply()
at
mx.core::UIComponent/mx.core:UIComponent::callLaterDispatcher2()[C:\dev\GMC\sdk\framework s\mx\core\UIComponent.as:7789]
at
mx.core::UIComponent/mx.core:UIComponent::callLaterDispatcher()[C:\dev\GMC\sdk\frameworks \mx\core\UIComponent.as:7732]
This error makes no sense...If we would've used a Pie chart
instead of a bar chart, everything would've worked just fine. Am I
doing something wrong here or is this a bug??
Thanks,
-george

Weldome to the very dificult topic of application domains.
This error is due to an idiosyncracy in how classes are
identified in Flex 2. Each instance of an application has its own
set of classes (application domain). The UIComponent in the main
SWF has a different identifier than the one in the loaded SWF, and
the second instance of the loaded SWF has yet another identifier
because a separate application domain is set up for each instance
of a SWF. To get things to work, they have to match, by having
everybody share the same class.
This works for UIComponent because loaded SWFs are configured
to use the classes in the loading SWF if they already exist. I'll
bet that if you put a columnChart in the loading SWF things will
get better.
That's not always a satisfactory solution because then the
loading SWF is sort of bloated, so then you have to try other
configurations to get things share classes properly. One
configuration is to put the charts in an RSL and load that at
run-time and then make instances of the Chart. Another is to put
the shared asset (I'm guessing you customized the axis stroke?) in
the main swf or RSL and load that before you load the Chart SWF.
What is probably happening underneath for you is that the
first instance sets up the styles for the columnChart including the
custom axis stroke. The second instance is going to end up using
that set of styles including the first instance's axisStroke which
is illegal because it is in an application domain that is
off-limits. They can only share the loading SWFs classes, and not
the sibling SWFs classes. Unfortunately, style definitions are
global.
How you solve this problem will be somewhat dependent on
whether you are only going to load two instances or N instances and
how many other assets need to be shared, and how comfortable you
are with RSLs

Unresolvec SWFLoader bug

Hello All
I have a problem with the swfLoader that bucket loads of
other people have as well and have posted on forums all over the
internet. Unfortunately, no solution has been found.
Basically, if you load a flex 2 app in to a swfloader, then
after interaction it loads another, then it has to load the
original one again, nothing is shown apart from the broken app
icon.
For example:
1. A button is clicked and the code
swfloader.source='one.swf' is used.
2. A second button is clicked and swfloader.source='two.swf'
is used to load another flex 2 app.
3. The first button is clicked again to perform line 1 above.
This is where the error is. The flex 2 app is not re-loaded and
just shows the broken app icon.
This really does seem to be a very common problem. Does
anyone know of a work around for this or even a solution or any
information at all about it?? Adobe are quiet about it too.....
Thanks,
Mike

Weldome to the very dificult topic of application domains.
This error is due to an idiosyncracy in how classes are
identified in Flex 2. Each instance of an application has its own
set of classes (application domain). The UIComponent in the main
SWF has a different identifier than the one in the loaded SWF, and
the second instance of the loaded SWF has yet another identifier
because a separate application domain is set up for each instance
of a SWF. To get things to work, they have to match, by having
everybody share the same class.
This works for UIComponent because loaded SWFs are configured
to use the classes in the loading SWF if they already exist. I'll
bet that if you put a columnChart in the loading SWF things will
get better.
That's not always a satisfactory solution because then the
loading SWF is sort of bloated, so then you have to try other
configurations to get things share classes properly. One
configuration is to put the charts in an RSL and load that at
run-time and then make instances of the Chart. Another is to put
the shared asset (I'm guessing you customized the axis stroke?) in
the main swf or RSL and load that before you load the Chart SWF.
What is probably happening underneath for you is that the
first instance sets up the styles for the columnChart including the
custom axis stroke. The second instance is going to end up using
that set of styles including the first instance's axisStroke which
is illegal because it is in an application domain that is
off-limits. They can only share the loading SWFs classes, and not
the sibling SWFs classes. Unfortunately, style definitions are
global.
How you solve this problem will be somewhat dependent on
whether you are only going to load two instances or N instances and
how many other assets need to be shared, and how comfortable you
are with RSLs

SWFLoader/Image complete event problem (bug?)

I have an SWFLoader in my application whose content is
dynamically bound to a datagrid for loading different images.
Depending on the new image size I want to make some adjustments,
etc. to the SWFLoader itself... that's not important for now.
The problem is that if I take the width of the SWFLoader
instance on the "complete" event, it gives the value for the
PREVIOUS image setting so my math function is useless.
Try this to see what I mean:
[Bindable]
public var imageSource:String;
private function temp():void {
mx.controls.Alert.show("imgLoader.width: "+imgLoader.width);
<mx:Button click="imageSource='someImageURL'" />
<mx:SWFLoader id="imgLoader" autoLoad="true"
source="{imageSource}" complete="temp()" />
if you implement the above code, and assuming that
imageSource is a null string upon initialization, you will get a
value of "0" for the imgLoader instance's width when you load a new
image.
To get around this in Flex 1.5 I could use doLater(this,
"temp") but doLater appears to have been removed in Flex 2.0.
My current work around is to modify the above code as
follows:
private function temp():void {
this.addEventListener("enterFrame", blorch);
private function blorch(b:Event):void {
mx.controls.Alert.show("imgLoader.width: "+imgLoader.width);
this.removeEventListener("enterFrame", blorch);
feels like a hack to me... is there no way to get this to
work without using the above functions? Sort of seems pointless to
have removed "doLater" just to make me write a function that
essentially does the same thing in Flex 2.0. I tried using the
"resize" event in place of "complete" and that works... if the
image loaded is a different size than the previous one. If the
image is the same size (as is often the case in my application)
then it doesn't work.
Any suggestions Adobe/Macromedia, fellow developers?

Flex harUI -
two solutions to this then are:
1) use the callLater() function or
2) extend the SWFLoader class...
I don't want to increase my component files so I will stick
with the callLater() setup.
Haskasu -
I tried init. It has the same result as complete. If I insert
code like this: init="mx.controls.Alert.show(imgLoader.width)" I
get the width for the *previous* setting (same as complete) and not
the new setting.

Another bug in Flex? (Application.parameters and query strings)

I'm passing in two query string parameters in the source of SWFLoader and both of them are clumped together in the first parameter by application.parameters.
But I switch the order of the parameters in the query string and both parameters are returned correctly:
Case #1:
Query String: ?cfg=zzzzzzz54B&embed_div=x
parameters.cfg: zzzzzzz54B&embed_div=x
parameters.embed_div: [nothing]
Case #2:
Query String: ?embed_div=x&cfg=zzzzzzz54B
parameters.cfg: zzzzzzz54B
parameters.embed_div: x
Here is the actual debug commands:
Dumper.info(this.url);
Dumper.info(this.parameters.cfg)
Dumper.info(this.parameters.embed_div);
And output:
(Case #1)
[INFO]: file:///C:/Program%20Files/WordRad234/chm/wordrad_kt/web%20pages/zzzzzzz5/rad_3xf.swf?cfg =zzzzzzz54B%26embed_div%3Dx (String)
[INFO]: zzzzzzz54B&embed_div=x (String)
[INFO]: (Object)
(Case #2)
[INFO]: file:///C:/Program%20Files/WordRad234/chm/wordrad_kt/web%20pages/zzzzzzz5/rad_3xf.swf?emb ed_div=x&cfg=zzzzzzz54B (String)
[INFO]: zzzzzzz54B (String)
[INFO]: x (String)
Something I just noticed: the equal sign after embed_div is replaced by %3D but only if embed_div comes last.

NEVERMIND:
It was something I was doing to the source of SWFLoader beforehand (involving encodeURIComponent).
I have to say, I have many, many times thought something was a bug in Flex and it was in fact my code. In general, I think Flex/AS3 is an elegant and useful product. The sort of ad hoc tweaks that have to be done to avoid memory leaks though is ridiculous (though I do have that figured out pretty much as well.)

A swf loader bug?

It looks like I may have found a bug in the swf loader. Before I submit this problem I want to make sure there is not something I'm missing in my code. I wrote this class to load a tutorial when the user first launches a sub application in a project I'm working on. This is a simplified version of the class that exemplifies the problem. The same methods I use to launch the swf from within an mxml work just fine, but when I externalize the process in this class, I can hear the tutorial, but I get no visual. Is this a bug or am I missing something?
Here is the tutorial launcher class:
package proj.fuego.utils
     import flash.events.Event;
     import mx.controls.SWFLoader;
     import mx.flash.UIMovieClip;
     public class TutPlayerSimple extends UIMovieClip
          private var gutLoader:SWFLoader;
          public function TutPlayerSimple(fullTutorialPath:String)
             gutLoader = new SWFLoader();
             gutLoader.addEventListener(Event.COMPLETE, addToStage);
             gutLoader.load(fullTutorialPath + ".swf");
             //addChild(gutLoader);
          private function addToStage(evt:Event):void
             addChild(evt.target.content);
This is my mxml:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" minWidth="1024" minHeight="768" applicationComplete="application1_applicationCompleteHandler(event)">
     <mx:Script>
          <![CDATA[
             import mx.controls.SWFLoader;
             import mx.events.FlexEvent;
             import proj.fuego.utils.TutPlayerSimple;
             private var fullTutorialPath:String = "ll_tut";
             private var tutPlayer:TutPlayerSimple;
             protected function application1_applicationCompleteHandler(event:FlexEvent):void
                  // TODO Auto-generated method stub
                  var context:LoaderContext = new LoaderContext();
                  tutPlayer = new TutPlayerSimple(fullTutorialPath);
                  //context.checkPolicyFile = true;
                  //gutLoader.loaderContext = context;
                  trace("Loading Tut:", fullTutorialPath + ".swf");
                  addChild(tutPlayer);
          ]]>
     </mx:Script>
</mx:Application>

That didn't look right. You'll need to addChild SWFLoader. Not sure what will happen if you just try to add its content. There might also be issues putting Flex components inside a UIMovieCip.
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui

Flex Applications loaded in SWFLoader DropDownList Offset

Hello all,
I have searched far and wide and am unable to come up with the answer to an issue I am experiencing. I have a Flash App (FB4) Which loads various other Flex 3 and 4 apps using SWFLoader based on what the user requires at the time.
Everything is working well so far with one exception. If I have the SWFLoader offset (Like Left="50" or Top="50") Then the dropdown menu that appears when a user clicks the DropDownList component is offset by that many pixels to the right or down. My goal is to provide a graphical menu above the embedded swf. However, when I do that each time the DropDownList is clicked, the list of choices is moved down by the same amount of pixels the embedded swf is on the stage. It appears to be a bug in the way the DropDownList works for determining location, but I don't know how to fix it.
Any thoughts?

Thank you for that. I have the loadcompatability option so I can have different versions. But I did not know about the compiler setting. Is there documentation somewhere about the compiler settting?

SWFLoader problem(make the whole application zoomed in Mac)

Hi,
I am using swfloader to load an swf. Everything works on different browsers in pc(safari, chorme, IE and ff). But when I launch this in safari in mac machine. whiling the application loading he swf file(same swf file(the size is 1024*720), whole application zoom in(everything become bigger).
Any help is appreciated.
flash player version 10.1
Thanks

This bug seems only happened if your screen's resolution is not a native resolution. For example, if your screen's native resolution is 1650*1024 and you set your screen resolution to be 1440 * 1050, the whole application will be zoomed once you are trying to loader a swf.
I believe this is a bug of flash player.

[svn] 2841: Fix bug loading untrusted applications that have not been sized .

Revision: 2841
Author: [email protected]
Date: 2008-08-14 04:45:09 -0700 (Thu, 14 Aug 2008)
Log Message:
Fix bug loading untrusted applications that have not been sized.
QE:YES
Doc:
Checkintests: YES
Reviewer: Alex
Bugs: SDK-16470
SWFLoader:
Fixed a security violation trying to access untrusted content. The problem happened in doScaleContent() when the loaded content had not been sized yet. The fall back is to check the class type of the content, but the SWFLoader did not have access to the content. The security violation was caught and the FlexLoader size is set when it shouldn't be. The problem is solved by checking access rights before accessing the content and not generating an exception.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16470
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/controls/SWFLoader.as

Ignoring what is causing the errors for a moment, what would help is a way to get the application loader to restart from the point of error rather than going back to the beginning of the "Loading applications" step each time.
I imagine this to be something of a big ask. Any other suggestions in a similar vein?
Nick.

SWFLoader Problems

I have a major application that involves a Flex application acting as a main container, and it loads loads other Flex applications into it via SWFLoader.
Originally, the main container was built in Flex 3 and I was loading Flex 4 child applications into it. This was working fine until the Flash Builder Beta 2 came out. So I decided I am going to port my main container from Flex 3 to the Flash Builder Beta 2 and I am having all sorts of problems with the SWFLoader implementation.
I want to have two different configurations for the SWF content to load into the SWFLoader.
The first configuration should be totally sandboxed such that the only way that the child SWF can communicate with any other SWF is via LocalConnection.
The second configuration should be such that individual child SWFs are in sibling ApplicationDomains so they can have their own Singletons of the same name, but, content needs to be able to be dragged and dropped from one child SWF to another child SWF. For instance, the child SWFs will often have AdvancedDataGrid implementations and they'll often need to be able to have content dragged from one to the other.
I currently have a SWFLoaderFactory class that has a static method as such:
        public static function getSWFLoader(sandbox:Boolean=true):SWFLoader
            // create the SWFLoader instance
            var swfLoader:SWFLoader = new SWFLoader();
            // not sandboxed
            if(!sandbox)
                swfLoader.loadForCompatibility = true;
            // sandboxed
            else
                var context:LoaderContext = new LoaderContext();
                context.securityDomain = SecurityDomain.currentDomain;
                context.applicationDomain = new ApplicationDomain();
                swfLoader.loaderContext = context;
            // return the SWFLoader instance
            return swfLoader;
This was working exactly as I needed it to when the main container was in Flex 3 but now in Flex 4 it is broken.
What happens is with the swfLoader.loadForCompatbility set to true, the following error occurs:
TypeError: Error #1009: Cannot access a property or method of a null object reference.
    at mx.controls::SWFLoader/initSystemManagerCompleteEventHandler()[E:\dev\gumbo_beta2\framewo rks\projects\framework\src\mx\controls\SWFLoader.as:2466]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.managers::SystemManager/initHandler()[E:\dev\beta1\frameworks\projects\framework\src\m x\managers\SystemManager.as:3197]
I'll add that the child SWFs will always be on a different domain than the parent SWF container.
I would appreciate it if someone could help me solve this problem once and for all and create the optimum configuration that will allow me to do what I want to do.

If it crashes consistently, file a bug with the SWFs involved.

[svn] 3571: Update SWFLoader ASDoc comment to remove &emdash and data type declaration .

Revision: 3571
Author: [email protected]
Date: 2008-10-10 11:07:09 -0700 (Fri, 10 Oct 2008)
Log Message:
Update SWFLoader ASDoc comment to remove &emdash and data type declaration. ASDoc adds that automatically.
Doc the new types in IndexChangedEvent.as
Checkin Test Passed: Yes
QA: No
Bug:
Doc: No
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/SWFLoader.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/events/IndexChangedEvent.as

lunke you shoude change svn update http://svn.foo-projects.org/svn/xfce/modules/trunk to svn up $startdir/src/trunk
hers a PKGBULID for thunar
pkgname=thunar
pkgver=0.0.2.r17470
pkgdesc="Thunar is a file manager designed for Xfce. It is currently under development."
url="http://thunar.xfce.org/wiki/"
depends=('exo-svn')
makedepends=('subversion')
source=()
md5sums=()
build() {
if [ ! -d $startdir/src/thunar ]; then
echo "Fetching sources..."
svn checkout http://svn.foo-projects.org/svn/xfce/thunar/trunk/ /thunar
else
echo "Updating sources..."
svn up $startdir/src/thunar/
fi
cd $startdir/src/thunar
./autogen.sh --prefix=/opt/xfce4-svn
make || return 1
make DESTDIR=$startdir/pkg install
find $startdir/pkg -name '*.la' -exec rm {} ;
you will need exo from svn as well
pkgname=exo-svn
pkgver=r17470
pkgdesc="Extensions to Xfce by os-cillation"
url="http://libexo.os-cillation.com/"
conflicts=(exo)
provides=(exo)
depends=('xfce4-svn')
makedepends=('subversion')
source=()
md5sums=()
build() {
if [ ! -d $startdir/src/trunk ]; then
echo "Fetching sources..."
svn checkout http://svn.foo-projects.org/svn/xfce/libexo/trunk/
else
echo "Updating sources..."
svn up $startdir/src/trunk
fi
cd $startdir/src/trunk
./autogen.sh --prefix=/opt/xfce4-svn
make || return 1
make DESTDIR=$startdir/pkg install
find $startdir/pkg -name '*.la' -exec rm {} ;
"Operation libtool-slay" compliant

[svn:osmf:] 15121: Fix bug related to validation of plugin versions.

Revision: 15121
Revision: 15121
Author:   [email protected]
Date:     2010-03-29 17:33:12 -0700 (Mon, 29 Mar 2010)
Log Message:
Fix bug related to validation of plugin versions. The fix is to load a dynamic plugin SWF twice. The first time it's loaded into a separate ApplicationDomain, so that the class types are not merged (and Version.version will not have identical values for player and plugin). If the version types are consistent, then the plugin is loaded a second time, this time into the same SecurityDomain (so that class types are merged). The second load should pull the SWF from the cache, minimizing the overhead. The downside is that the SWF will be initialized twice.
Modified Paths:
    osmf/trunk/framework/OSMF/org/osmf/elements/SWFLoader.as
    osmf/trunk/framework/OSMF/org/osmf/elements/loaderClasses/LoaderUtils.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/DynamicPluginLoader.as
    osmf/trunk/framework/OSMF/org/osmf/media/pluginClasses/PluginLoader.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/media/pluginClasses/TestPluginManagerIn tegration.as
    osmf/trunk/framework/OSMFIntegrationTest/org/osmf/utils/IntegrationTestUtils.as

Hi sebasvideo, Did you ever find a solution to this? I've been having the same problem for a few months now and it's maddening. Seems to be specific to the GPU like you say above. I noticed it most when using Element 3D. I thought maybe there was some sort of read/write interference as I have 2 SSDs and one HD with assets spread across all of them. But even when I consolidated all of my data to one drive the flickering kept happening. Not sure if it's an After Effects problem specifically... or windows 8.1? Or nVidia? Super frustrating thoguh.

[svn] 3520: Add ability to use the FP10 unloadAndStop() method in SWFLoader .

Revision: 3520
Author: [email protected]
Date: 2008-10-08 10:26:39 -0700 (Wed, 08 Oct 2008)
Log Message:
Add ability to use the FP10 unloadAndStop() method in SWFLoader.
An application needs to be compiled with the "-target-player=10" argument to allow SWFLoader's unloadAndStop() function to use the Flash Player's unloadAndStop() function. If the argument is not provided then the Flash Player unload() function will be called instead.
QE: YES
Doc: YES
Checkintests: YES
Reviewer: Ely, Deepa
Bugs: SDK-16764
SWFLoader.as
Added new public method unloadAndStop().
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16764
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/controls/SWFLoader.as

Thank you for your replies.
I have been looking into it as well and seem to have found quite a simple solution...
First you need to create an instance of a UIScrollView in the .h file:
IBOutlet UIScrollView *scrollView;
Then in the .m file, add the following line of code in the viewDidLoad method:
scrollView.contentSize = CGSizeMake(320, 700);
Then in IB all you need to do is set the files owner to the controller file we have set up above, drag a new instance of UIScrollView to the window. Then set two of its referencing objects to the File's Owner (view and the scrollView we have defined).
You can then add as many labels etc to the scroll view by dragging in IB. Load it all up and the view scrolls perfectly and displays all labels!
Thanks for helping me look into this.

[svn:fx-trunk] 10065: Comment out code causing an RTE in SWFLoader.

Revision: 10065
Author:   [email protected]
Date:     2009-09-08 13:14:26 -0700 (Tue, 08 Sep 2009)
Log Message:
Comment out code causing an RTE in SWFLoader. Will fix as part of per-module styles feature development.
QE notes: None.
Doc notes: None.
Bugs: SDK-23081
Reviewer:
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23081
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/SWFLoader.as

Hello, first post here..
I maintain a java based lobby for an opensource RTS
engine called spring at http://taspring.clan-sy.com
You can find my lobbys source code at:
https://taspring.clan-sy.com/svn/spring/trunk/AFLobby/
Of note being the unitsync.dll/so library used to
handle mods and maps. Implementing this library in
pure java is not an option.
I've dealt with quite a few JNi errors dealing with
the linux users but we got through them all and it
all worked great.
I released a windows installer, and most users can
run it fine with no issues with JNI, but 2 users seem
to have problems, despite correctly installing
everything.Does the JNI code use perl?
This error message shows several hits on Google for perl related stuff.

Error with SwfLoader and new application domain

Hi
I have a test with a SWFLoader loading an application in a different application domain.
Test with SWFLoader is ok when you load the application in the same application domain but when I want a new Application Domain, I have an error message with a flahplayer debug version when I use the unload method.
Is this a bug ?

I use FlexUnit 4 and FlexBuilder 3
I want to test the behaviour of a custom class which extends SWFLoader,
including when it loads (and unloads) an application in a new
application domain, but I have this error message so I tried some very
simple tests on SWFLoader.
In my test I just load a swf file in a new application domain and unload
it when it's completed. On the "unloadAndStop" method I have this error
message :
TypeError: Error #1009:
    at
mx.managers::SystemManager/removeChildBridge()[C:\autobuild\3.3.0\frameworks\projects\fram ework\src\mx\managers\SystemManager.as:4844]
    at
mx.controls::SWFLoader/contentLoaderInfo_unloadEventHandler()[C:\autobuild\3.3.0\framework s\projects\framework\src\mx\controls\SWFLoader.as:2160]
    at flash.display::Loader/_unload()
    at flash.display::Loader/unloadAndStop()
    at
mx.controls::SWFLoader/load()[C:\autobuild\3.3.0\frameworks\projects\framework\src\mx\cont rols\SWFLoader.as:1334]
    at
mx.controls::SWFLoader/commitProperties()[C:\autobuild\3.3.0\frameworks\projects\framework \src\mx\controls\SWFLoader.as:1185]
    at
mx.core::UIComponent/validateProperties()[C:\autobuild\3.3.0\frameworks\projects\framework \src\mx\core\UIComponent.as:5807]
    at
mx.managers::LayoutManager/validateProperties()[C:\autobuild\3.3.0\frameworks\projects\fra mework\src\mx\managers\LayoutManager.as:539]
    at
mx.managers::LayoutManager/doPhasedInstantiation()[C:\autobuild\3.3.0\frameworks\projects\ framework\src\mx\managers\LayoutManager.as:689]
    at Function/http://adobe.com/AS3/2006/builtin::apply()
    at
mx.core::UIComponent/callLaterDispatcher2()[C:\autobuild\3.3.0\frameworks\projects\framewo rk\src\mx\core\UIComponent.as:8633]
    at
mx.core::UIComponent/callLaterDispatcher()[C:\autobuild\3.3.0\frameworks\projects\framewor k\src\mx\core\UIComponent.as:8573]

SWFLoader Bugs?!!!!!!!!!!!!!

Similar Messages

Maybe you are looking for