FMX.ListView.TCustomListView.Destroy
C++
/* TAppearanceListView.Destroy */ inline __fastcall virtual ~TCustomListView() { }
Properties
| Type | Visibility | Source | Unit | Parent |
|---|---|---|---|---|
| destructor | public | FMX.ListView.hpp | FMX.ListView | TCustomListView |
Description
Disposes of the component and its owned components.
FMX.ListView.TCustomListView.Destroy inherits from System.Classes.TComponent.Destroy. All content below this line refers to System.Classes.TComponent.Destroy.
Disposes of the component and its owned components.
Do not call Destroy directly. Call Free instead. Free verifies that the component is not nil, and only then calls Destroy.
Never explicitly free a component in one of its own event handlers, nor free a component from the event handler of a component that it owns or contains.
To destroy a form, call its Release method. Release waits for all the form's event handlers and the event handlers of the form's components to finish executing before destroying the form.
Note: A form owns all the controls and nonvisual components that are placed on it in design mode. When it is freed, all of these components are automatically freed as well. By default, all forms are owned by the global Application object. When an application terminates, it frees the global Application object, which frees all forms. For objects that are not components, and for components created with a nil owner, be sure to call Free after finishing with the object; otherwise the memory allocated for the object will be lost until the application terminates.