Re: Automated testing for Flex applications

2014-01-03 Thread Mihai Chira
Heya, Do we have flexunit compiled for the latest version of the SDK? Because I have a class that extends ListCollectionView's removeItem() function, which was added in v. 4.10 [1]. So when I try to run the unit test, it says Suspended: VerifyError: Error #1053: Illegal override of removeItem

Re: Automated testing for Flex applications

2014-01-03 Thread Gary Young
Mihai, I use Flexmojos, so I don't encounter the same problem, I think FlexUnit is a part of Apache Flex now: https://github.com/flexunit/. hope this can help a little. -Gary On Fri, Jan 3, 2014 at 7:15 AM, Mihai Chira mihai.ch...@gmail.com wrote: Heya, Do we have flexunit compiled for the

Re: Automated testing for Flex applications

2014-01-03 Thread Mihai Chira
Thanks Gary, I did see the repo, but the latest commit seems to have been made 3 years ago (except for the readme file). Which suggests to me that it's not compiled against newer SDKs. If that's confirmed by others who know more, I might take a look and try to migrate it myself. On 3 January

Problem with states not working as before without code change (only SDK)

2014-01-03 Thread Fréderic Cox
I have a confirmed bug in a module of a CMS I worked on in the past 2-3 years. The only change now is that I use Apache Flex 4.10. I use includeIn for showing buttons in states. Since the migration from Flex 4.1 or 4.6 to 4.10 it is not working anymore. So I am not entirely sure if the change in

Re: Problem with states not working as before without code change (only SDK)

2014-01-03 Thread Fréderic Cox
Important to note that when going to batchMode state the buttons are correctly shown. Only when going back to normal there is nothing happening anymore and the buttons seem to have dissapeared. No buttons are showing at that moment. -- View this message in context:

Re: Problem with states not working as before without code change (only SDK)

2014-01-03 Thread Alex Harui
It looks like you are using both visible and includeIn. It might be that since 4.1, properties are restored differently and visible is not being set back to true? You can use the -keep-generated-actionscript MXMLC option to see if anything is being generated differently, and if not, see if logic