I obviously have not been following well enough. What was the reason for this change?
On Oct 13, 2016, at 8:52 AM, Alex Harui <aha...@adobe.com> wrote: > Getters and Setters should now generate a get__ and set__ method. So on > your class A if you have: > > override public function set visible(value:Boolean):void > > You should get: > > A.prototype.set__visible(value) > > Super calls should then generate calls to base so > > super.visible = value; > > Should produce: > > A.base(this, 'set__visible', value); > > If that is all true, next step is to debug into the base() call. I > thought base() knew how to look up through the chain of ancestor classes > and didn't expect that the super call was on the immediate ancestor. A > workaround might be to temporarily inject an override on each ancestor > class. > > Or if Core hasn't been re-compiled recently, then there won't be a > set__visible call in it for base() to find. > > HTH, > -Alex > > On 10/12/16, 10:11 PM, "yishayw" <yishayj...@hotmail.com> wrote: > >> On the JS side I'm getting >> >> base.js:2498 Uncaught TypeError: Cannot read property 'apply' of undefined >> >> For this line in base.js: >> >> return parentCtor.prototype[methodName].apply(me, args); >> >> where methodName is set__visible >> >> The AS code is: >> >> super.visible = value; >> >> for a method in class A which extends class B which extends >> GraphicContainer >> which extends UIBase >> >> I'm using nightly build falcon from 2 days ago. >> >> Any ideas? >> >> Thanks >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://apache-flex-development.2333347.n4.nabble.com/FlexJS-super-method-c >> alls-broken-tp55727.html >> Sent from the Apache Flex Development mailing list archive at Nabble.com. >
