I would assume that all these components would have
unique Names? If so, why not create a global procedure that would delete/free
components by Name. Inside this procedure would dynamically cycle through all
the components/controls using the Controls property (remember to do this
recursively so that you can get down into the deepest level of
parentship) and delete the appropriate one. You could also use the Tag
instead of the Name of course.
An alternative would be to have a global TList
where you "register" all the dynamic components created. You can then use this
TList instead of the Form to traverse the list of dynamically created components
(it may be a bit easier than the recursive approach mentioned
above).
It all depends on what criteria is used (and how
the selection is made) on what components you want to delete....
Hope this helps
Xander
|
- [DUG]: Multiple Dynamic Components Jeremy Coulter
- RE: [DUG]: Multiple Dynamic Components Paul Heinz
- RE: [DUG]: Multiple Dynamic Components Jeremy Coulter
- RE: [DUG]: Multiple Dynamic Components Xander van der Merwe
- RE: [DUG]: Multiple Dynamic Components Dennis Chuah
- Re: [DUG]: Multiple Dynamic Components Neven MacEwan
- Re: [DUG]: Multiple Dynamic Components Peter Hyde
- [DUG]: Delphi contractors needed... Mark Vrankovich
- RE: [DUG]: Multiple Dynamic Components David O'Brien