It's an issue for anyone developing nested components. In my case I have a component that I want to distribute that creates some (global) data that I want to tidy up / clear when the component is deleted manually or by script. This is fine if the group is a top level group, but as i use "layout groups" and other forms of group nesting (say I want to use the group within a datagrid for instance) - then no message at all is sent - and so I cannot create this form of component without resorting to libraries or front/back scripts.
I've filed this as a report here (and copied Trevor's description) - http://quality.runrev.com/qacenter/show_bug.cgi?id=8524 Votes appreciated! 2010/1/7 Trevor DeVore <[email protected]> > > Assume you have this group hierarchy: > > Group A > Group B > Group C > > If you delete Group B then Group B receives the deleteGroup message as does > Group A (unless Group B traps the message). > > If you delete Group A then Group B and Group C DO NOT receive the > deleteGroup message. Only Group A does. > > Currently a developer needs to to manually go through a group's children > and dispatch the deleteGroup message to it's children if it was the target > of the deleteGroup message. > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
