Hi Mike It would be helpful, if you could provide a link to the source of a minmal running example of this problem
Cheers Ralf. On 11/6/07, Mike Krotscheck <[EMAIL PROTECTED]> wrote: > > A bit more information: > > > > I am attempting to initialize a series of bindings in an "Abstract" class. > For the sake of argument, lets say that we have the class Abstract, the > class Child, are extending Canvas, and are attempting to bind to a singleton > data model. During childrenCreated I'm calling a protected method called > initializeBindings(). This method is extended in the child. > > > > Both the child and abstract versions of initializeBindings create a > binding using BindingUtils and "this". The child class calls > super.initializeBindings(). > > > > Observed behavior: > > Case 1: super.initializeBindings() is called before child > BindingUtil.bindProperty() > > Debugger shows that "this" reference in child is appropriate. > Shows that "this" reference in abstract has same memory address, but > contains only _bindingsBeginWithWord and _bindingsByDestination. After > attempting to call BindingUtil.bindProperty in the abstract class, the > runtime environment *fails silently* and the stack is terminated (child's > binding never gets called). Binding in the abstract class is never created. > > > > Case 2: super.initializeBindings() is called after child > BindingUtil.bindProperty() > > Same as above regarding "this", but in this case the binding > created by the child has been created. The abstract has not. > > > > I've tested this both in 2.0 hotfix 3 and 3.0b2. Any pointers? I'd like to > avoid creating these bindings in the child class, since due to the nature of > code-generated bindings they interfere with garbagecollection, and the > abstract class actually contains some destruction functionality. > > > > *Michael Krotscheck* > > Senior Developer > > > > > *RESOURCE INTERACTIVE* > > <http://www.resource.com/>www.resource.com > > [EMAIL PROTECTED] > > > ____________________________________________________________________________ > This email and any of its attachments may contain Resource Interactive > proprietary information, which is privileged, confidential and may be > subject to copyright or other intellectual property rights belonging to > Resource Interactive. This email is intended solely for the use of the > individual or entity to which it is addressed. If you are not the intended > recipient of this email, you are hereby notified that any dissemination, > distribution, copying or action taken in relation to the contents of and > attachments to this email is strictly prohibited and may be unlawful. If you > have received this email in error, please notify the sender immediately and > permanently delete the original and any copy of this email and any printout. > ------------------------------ > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Mike Krotscheck > *Sent:* Tuesday, November 06, 2007 5:07 PM > *To:* [email protected] > *Subject:* [flexcoders] "this" in parent classes > > > > I've discovered you can't use "this" to refer to the current instance from > the parent class. Is there another way I can reference the currently > instantiated child? > > > > *Michael Krotscheck* > > Senior Developer > > > > > *RESOURCE INTERACTIVE* > > <http://www.resource.com/>www.resource.com > > [EMAIL PROTECTED] > > > > * > ____________________________________________________________________________ > * > *This email and any of its attachments may contain Resource Interactive > proprietary information, which is privileged, confidential and may be > subject to copyright or other intellectual property rights belonging to > Resource Interactive. This email is intended solely for the use of the > individual or entity to which it is addressed. If you are not the intended > recipient of this email, you are hereby notified that any dissemination, > distribution, copying or action taken in relation to the contents of and > attachments to this email is strictly prohibited and may be unlawful. If you > have received this email in error, please notify the sender immediately and > permanently delete the original and any copy of this email and any printout. > * > > >
