Its against the very basic design principle of OOP "Loose coupling and High Cohesion". Similarly the practice of using Application.application. ... is highly discouraged.
Akhil Mittal On Jun 24, 8:54 am, [email protected] wrote: > you may end up adding/removing more parent/child. In that case you then have > to rewrite the code in order to refer your container. Nothing else i can > think of > > > > On Wed, Jun 23, 2010 at 17:29, Ajantha <[email protected]> wrote: > > Hi , > > > I would like to know why using event.parent.parent.parent .. in > > order to get to an instance a bad practise?? > > > can someone explain ? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Flex India Community" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<flex_india%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/flex_india?hl=en. > > -- > Fear is an illusion, So, face it ! > RM3sh -- You received this message because you are subscribed to the Google Groups "Flex India Community" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/flex_india?hl=en.
