Unlike the VCL, KOL does not have an Owner property for components. Ownership is implemented here by the Add2AutoFree [Ex] method. If you use MCK to create a project, then all objects of the form are attached to the object-holder of the form precisely by calling the Add2AutoFree [Ex] methods in order to ensure that they are automatically destroyed along with the form when its existence ends. For visual objects, there is a Parent property (and others accompanying it), which uniquely defines the relationship between a parent window and a child window in the Windows environment. Just like in the VCL, through the Parent property, you can change the parent of a visual object dynamically, at runtime. But not always: for example, the combo box does not allow such liberties, this is the behavior of the Windows API.

 

Parent - reference (PControl) to the parent window object (may be absent for top-level windows (for Applet and for forms), as well as in the case when the window was created as a child in relation to someone else's window (in the latter case, the parent is indicated by ParentWindow);

ParentWindow - returns a handle to the parent window;

ParentForm - looks through all the parents up the chain, and returns the object of the form on which the given window object lies;

ChildCount - returns the number of child window objects;

Children[i] - returns a pointer (PControl) for the i-th child element in the list (note: KOL still retains the MembersCount and Members [i] properties, but this is a "tail" that has been going on since the XCL days, in reality these properties are not needed, enough ChildCount and Children [i]);

ChildIndex(C) - returns the index of the specified child window object (or -1 if such an object is not found in the list of children);

MoveChild(C, i) - "moves" child "control" to the specified position in the list of child objects;

IsControl - checks that the object is exactly a "control" (that is, not a form or an applet).