|  | Home · All Classes · Main Classes · Grouped Classes · Modules · Functions |

# Object Trees and Object Ownership

### Overview

QObjects organize themselves in object trees. When you create a QObject with another object as parent, it's added to the parent's children() list, and is deleted when the parent is. It turns out that this approach fits the needs of GUI objects very well. For example, a QShortcut (keyboard shortcut) is a child of the relevant window, so when the user closes that window, the shorcut is deleted too.

QWidget, the base class of everything that appears on the screen, extends the parent-child relationship. A child normally also becomes a child widget, i.e. it is displayed in its parent's coordinate system and is graphically clipped by its parent's boundaries. For example, when the application deletes a message box after it has been closed, the message box's buttons and label are also deleted, just as we'd want, because the buttons and label are children of the message box.

You can also delete child objects yourself, and they will remove themselves from their parents. For example, when the user removes a toolbar it may lead to the application deleting one of its QToolBar objects, in which case the tool bar's QMainWindow parent would detect the change and reconfigure its screen space accordingly.

The debugging functions QObject::dumpObjectTree() and QObject::dumpObjectInfo() are often useful when an application looks or acts strangely.

### Construction/Destruction Order of QObjects

When QObjects are created on the heap (i.e., created with new), a tree can be constructed from them in any order, and later, the objects in the tree can be destroyed in any order. When any QObject in the tree is deleted, if the object has a parent, the destructor automatically removes the object from its parent. If the object has children, the destructor automatically deletes each child. No QObject is deleted twice, regardless of the order of destruction.

When QObjects are created on the stack, the same behavior applies. Normally, the order of destruction still doesn't present a problem. Consider the following snippet:

     int main()
     {
         QWidget window;
         QPushButton quit("Quit", &window);
         ...
     }

The parent, `window`, and the child, `quit`, are both QObjects because QPushButton inherits QWidget, and QWidget inherits QObject. This code is correct: the destructor of `quit` is not called twice because the C++ language standard (ISO/IEC 14882:2003) specifies that destructors of local objects are called in the reverse order of their constructors. Therefore, the destructor of the child, `quit`, is called first, and it removes itself from its parent, `window`, before the destructor of `window` is called.

But now consider what happens if we swap the order of construction, as shown in this second snippet:

     int main()
     {
         QPushButton quit("Quit");
         QWidget window;

         quit.setParent(&window);
         ...
     }

In this case, the order of destruction causes a problem. The parent's destructor is called first because it was created last. It then calls the destructor of its child, `quit`, which is incorrect because `quit` is a local variable. When `quit` susequently goes out of scope, its destructor is called again, this time correctly, but the damage has already been done.