Open GoogleCodeExporter opened 9 years ago
We've reproduced the problem and are investigating.
Original comment by eric.owe...@gtempaccount.com
on 20 Jul 2009 at 2:17
It looks like this is a known problem with the Flex Automation system. Please
see:
https://bugs.adobe.com/jira/browse/FLEXENT-1020
It also looks like Adobe is saying that this is solved in the (Beta) Flex 4
automation system, and that they don't
plan to solve it for Flex 3. FlexMonkey will support Flex 4 automation later
this year.
Adobe provides the source code for part of the Automation system to owners of
Flex Pro licenses, but not all.
It's our experience that about 50% of the time, problems in the automation
system can be tracked down and
fixed in this code -- for instance, a custom version of an Automation Delegate
with the fix.
We'll investigate further, but I can't provide a timeframe for a fix.
Original comment by eric.owe...@gtempaccount.com
on 20 Jul 2009 at 4:44
Ah well, thanks for looking into it. It's helpful to know it's a problem across
the board with testing Flex 3 AIR
apps.
Original comment by googlegr...@gersic.com
on 20 Jul 2009 at 6:19
Original issue reported on code.google.com by
googlegr...@gersic.com
on 17 Jul 2009 at 6:22