Hi Apologies for causing the extra hassle here. There doesn't appear to be a way for us to specify an API to be removed from the AS3 definitions at a particular SWF version, which actually meant we couldn't add the changes in a version-checked manner (i.e. our initial aim was to adjust the API based on the -swf-version value but we can only add new APIs in this way, rather than changing an existing one).
We've investigated the impact here a little further, and it looks like (for overriding the functions): 1) when you build the existing code (without the new parameters) then you need to use the old airglobal.swc file for this 2) an app built using the old airglobal.swc then won't run on the new AIR runtime 3) an app built using the new airglobal.swc then won't run on an older AIR runtime Part 3 here is what would also be the case if you were just using the new APIs: our original intent was that if you chose to use the new API then of course you need to compile with AIR 33.1 SDK and run it on AIR 33.1. I was going to suggest that the Flex code could be updated to add in the extra parameters for these overrides but I think we would still have an issue with #2, i.e. existing Flex applications will not work if run on AIR 33.1... That's definitely not a good thing, in my opinion! So I think we need to rethink this one; I would suggest holding off making any code changes here (i.e. don't use AIR 33.1!) as there may be some other options here (the obvious one being, revert the APIs...) thanks Andrew -----Original Message----- From: Greg Dove <greg.d...@gmail.com> Sent: 03 March 2020 20:32 To: users@flex.apache.org Subject: [EXTERNAL] Re: Flex 4.16.1 broken for AIR33.1? That sounds like there might be a few of these. Any classes that extend the native ones inside mx.geom will likely need attention for the affected overridden methods. On Wed, Mar 4, 2020 at 9:00 AM leokan23 <l...@best-web.gr> wrote: > Changing the -swf-version didn't do the trick. This is the change they did: > > /Update geometry APIs to allow object pooling, so for example, rather > than creating and returning new Point, Matrix, Vector3D etc objects, > functions within the flash.geom.* classes will take an optional > parameter that can be an object to reuse and return. / > > I will try messing around with Transform.as next. > > > > > > > -- > Sent from: > https://clicktime.symantec.com/3PG82YtwHLcZuLsBDbCLtTt7Vc?u=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F >
