Controls arrays, run-time VCL creation
Managing Run-Time Component Arrays
Learn how to access a group of programatically created components - by storing the components in an array.
How to Dynamically Add Items (Holding Custom Properties) to a TPopUp Delphi Menu
How to add menu items to a Menu (or Popup menu) at run-time, how to respond to the OnClick event. Plus: how to extend the TMenuItem to hold custom string property.
A warning on dynamically instantiating Delphi components
If you want to dynamically instantiate a Delphi component and explicitly free it sometime later, always pass nil as the owner. Failure to do so can introduce unnecessary risk, as well as performance and code maintenance problems. Read the article to learn more...
Creating Delphi components dynamically (at run-time)
Most often when programming in Delphi you don't need to dynamically create a component. If you drop a component on a form, Delphi handles the component creation automatically when the form is created. This article will cover the correct way to programmatically create components at run-time.
Creating forms at run-time
This article demonstrates techniques available when creating and closing modal forms and how one form can retrieve user input or other data from a secondary form.
How to Move and Resize Controls at Run Time
While in most situations you will arrange all the controls on a Delphi form in a "fixed" position, there are situations when you need to allow a user to change the placement and dimension of controls at run-time.
The role of the "AOwner" parameter in the Create constructor of Delphi components
Delphi must be destroying the objects, but how does it know when we’re through with them? Who ownes the component you create at run-time?
TForm.Create(?) Nil, Self or Application?
When creating Delphi objects dynamically, that inherit from TControl, such as a TForm (representing a window) in Delphi application, the constructor "Create" expects an Owner parameter. Should you use "nil", "self" or "Application"? Find here...
Visual Form Inheritance: Part I
VFI refers to Delphi's ability to create new forms that either inherit, or are derived from, existing forms.
Visual Form Inheritance: Part II
This article describes a basic framework you can use as the basis for your data-editing forms.