Closed GoogleCodeExporter closed 8 years ago
Please make sure you have the following includes when compiling the
FlexMonkeyLauncher.
-include-libraries "/Applications/Adobe Flex Builder 3/sdks/3.2.0/
frameworks/libs/automation.swc"
-include-libraries "/Applications/Adobe Flex Builder 3/sdks/3.2.0/
frameworks/libs/automation_agent.swc"
-include-libraries "/Applications/Adobe Flex Builder 3/sdks/3.2.0/
frameworks/libs/automation_dmv.swc"
Original comment by mark.c...@gorillalogic.com
on 24 Feb 2009 at 6:09
I recompiled with those three files and now am getting the following error:
VerifyError: Error #1053: Illegal override of removeChildBridge in
mx.managers.SystemManagerProxy.
Original comment by mmwhitak...@gmail.com
on 24 Feb 2009 at 7:23
The error you are getting now is due to version mismatch of the FlexMonkey and
your
application. FlexMonkey 0.8 is compiled with Flex 3.2. I would suggest you
download
the source and compile FlexMonkey, FlexMonkeyLauncher and your application.
Original comment by mark.c...@gorillalogic.com
on 24 Feb 2009 at 7:38
I downloaded and compiled the applications and I am no longer getting the #1053
Error. Now, I am having the same problem as described in Issue 29, where
anywhere
in my application, I reference "Application.application", then it references
FlexMonkey instead of my application under test. So in the following example,
I
have a component called windowShadeSearch that I am trying to access using
Application.application.windowShadeSearch and I get the following error only
when
loaded in FlexMonkeyLauncher:
Example:
ReferenceError: Error #1069: Property windowShadeSearch not found on
FlexMonkeyLauncher and there is no default value.
at turningpage.browser::History$/updateUrl()
[C:\Dev\Apps\blazeds_turnkey\tomcat\webapps\TurningpageFlex\flex\turningpage\bro
wser\
History.as:279]
at Main/__windowShadeSearch_click()
[C:\Dev\Apps\blazeds_turnkey\tomcat\webapps\TurningpageFlex\flex\Main.mxml:594]
Original comment by mmwhitak...@gmail.com
on 25 Feb 2009 at 1:26
At this point in time, the work around is to link FlexMonkey into your
application
instead of using the launcher. The directions for doing that can be found at
http://code.google.com/p/flexmonkey/wiki/LinkingFlexMonkeyIntoApp.
Original comment by mark.c...@gorillalogic.com
on 5 Mar 2009 at 4:09
Retiring 0.x issues
Original comment by eric.owe...@gtempaccount.com
on 16 Jul 2009 at 12:51
Original issue reported on code.google.com by
mmwhitak...@gmail.com
on 24 Feb 2009 at 3:23