Avoiding leaks with layout managers

**invictus** · 21st March 2007, 18:53

Originally Posted by jpn

The layout manager becomes a child of the widget it is installed on so you don't need to delete it by hand.

How about buttons, textfields, checkboxes, etc?

**jpn** · 21st March 2007, 19:53

Originally Posted by invictus

How about buttons, textfields, checkboxes, etc?

The layout manager handles reparenting of them. All widgets added to a layout become also children of the widget the layout is installed on.

**invictus** · 21st March 2007, 20:13

So basicly I never have to delete any component that is displayed on another widget?

Will there be problems if I do delete something that is a child of a widget?

**jpn** · 21st March 2007, 20:24

QObjects delete their children automatically and inform their parent when they get deleted. In addition, all relevant signal slot connections are also cleaned up. You are free to delete QObjects when you feel so with the exception that the sender of a signal must not be deleted in a slot.

Further reading: Object Trees and Object Ownership, notice QObject::dumpObjectTree() which is handy for examining object trees.