Hi Ajantha, If you use a hard reference like event.parent.parent.parent, there are chances that you may end up with run time errors. Because, if you move/add/remove any of the component/control in the hierarchy "parent.parent.parent" , then this will point to a wrong reference, which will lead to run time errors. If your intention is to access any control/object, then you can pass the reference of that control/object in the event directly. No matter, whatever is changed, the event will always carry the reference of the intended control/object
On Jun 23, 4:59 pm, 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]. For more options, visit this group at http://groups.google.com/group/flex_india?hl=en.
