Why Do Some Delphi Components Require "AOwner: TComponent" To Construct Them?

Question

It seems completely irrelevant to require a TComponent as an owner to instantiate an object of some kind. Why are there so many Delphi components that require this?

For example, TXMLDocument requires a TComponent object to instantiate.

Why is this and if there's a good reason, what should I be using in there to "do the right thing"?

Answer 1

The owner component is supposed to manage all its owned components. The owned components gets destroyed automatically when the owner is destroyed. This helps the developer who just drags components from the tool-palette, drops them on the form and just hooks up the events to get his work done without worrying about managing the lifetime of the components.

The form is the owner of all components dropped on it. The Application object is owner of the form. When the app is closed the Application object is destroyed which in turn destroys the forms and all the components.

But the owner is not really necessary when a components is created. If you pas Nil to the parameter, the component will be created without an owner. But it will be the programmer's responsibility to manage the component's lifetime.

Answer 2

All TComponent descendents require Owner, it is defined in TComponent constructor. The Owner component is responsible to destroy all the Owned components.

if you want to control the life time, you can pass nil as parameter.

Answer 3

Just to add some extra information.

Each control also has a parent. (A TWinControl). Where the owner takes care of the lifetime, the parent takes care of showing the object.

For example a form has a panel and the panel has a button. In that case, the form owns the panel and the button. But the form is the parent of the panel and the panel is the parent of the button.

Answer 4

There is also something else to be aware of. I have used more than a couple of third party components which rely on an Owner component being passed in the Constructor Create, and if you pass in Nil will throw an exception/AV.

The net result is that these components will work fine when you use the visually within the IDE but cause problems when they are created at run-time.

The cause of these problems is, in a sense, bad design. Nothing in the rules state you cannot/should not pass in NIL as the aOwner parameter.

Answer 5

The object doesn't REQUIRE a tComponent be passed as AOwner. You can easily pass nil to this and handle the destruction yourself. Most often, I tend to use this technique for localized routines where the component being used will not be used outside of the current method. for example:

Procedure TForm1.Foo;
var
  XmlDoc : tXmlDocument;
begin
  XmlDoc := tXmlDocument.Create(nil);
  try
    // do processing of the XMLDoc here
  finally
    FreeAndNil(XmlDoc); 
  end;
end;