Open GoogleCodeExporter opened 8 years ago
[deleted comment]
I am seeing this too.
Flex Monkey 1.0
Flash Player 9.0.124.0
Windows XP SP 3
Original comment by Intervalia
on 16 Jul 2009 at 5:10
Hi Folks:
We've reproduced the problem, and for us, at least initially, it only affects
running in the FlexMonkey Target
SWF window. When we run with the MonkeyAgent, modules are loaded.
If you can, please try the MonkeyAgent mode.
I'll let you know when I learn more.
Cheers,
Eric
Original comment by eric.owe...@gtempaccount.com
on 16 Jul 2009 at 6:04
I guess I should have stated that mine was in MonkeyAgent mode.
We were unable to load our app in the FlexMonkey target window. We errored out
in a
way that we were unable to track. So we were reuired to load our swf to be
loaded in
the browser.
Original comment by Intervalia
on 16 Jul 2009 at 6:40
[deleted comment]
More info about our setup can be found here:
http://groups.google.com/group/flexmonkey/browse_thread/thread/c426f7da217d53bc
Original comment by Intervalia
on 16 Jul 2009 at 6:42
I'm still unable to reproduce any module loading problems with the MonkeyAgent.
If anyone has a testcase that
reproduces this problem, please send it to me.
Original comment by eric.owe...@gtempaccount.com
on 12 Aug 2009 at 10:18
I may have a little insight here... Not sure if it's the same problem, but it
might shed
some light on why some people have problems with multi-module projects.
My modules load fine, however if any of the loaded Modules use classes that are
built/contained in the primary Application, I encounter errors.
I believe this problem stems from the ApplicationDomain problem listed in the
user docs. A
standard work-around when working with multi-module projects (to thwart
module-loading
issues) is to specify unused declarations as private member variables at the
mx:Application
level. This ensures proper scoping of shared code libraries across modules.
In my
application, this works fine when it's loaded in its own ApplicationDomain.
However, when
FlexMonkey loads the "targetSwf", it does so in the FlexMonkey
ApplicationDomain, rather
than my own. This means that in order to reference those shared code libraries
(shared
between my parent application and sub-modules), those libraries would need to
be included
inside (I'm assuming) MonkeyTestLauncher.mxml.
I noticed that "LT" made this post on the FlexMonkey Google Groups site.
(http://groups.google.com/group/flexmonkey/browse_thread/thread/644361bf1452c460
?pli=1) I'm
going to attempt his solution and see if it helps me as well.
Original comment by tvanbusk...@gmail.com
on 30 Sep 2009 at 1:13
Original issue reported on code.google.com by
scham...@gmail.com
on 15 Jul 2009 at 7:55