Differences

This shows you the differences between two versions of the page.

--- qt:heap_versus_stack [2010/12/08 22:17] – [Long answer] mithat
+++ qt:heap_versus_stack [2010/12/08 22:59] (current) – mithat
@@ Line 6: / Line 6: @@
 If the object is going to be part of a tree of Qt objects (as will be the case for most Qt GUI objects), then it should be created on the heap.
-If the object is not part of a tree or is the root of a tree, then it can be created either on the heap or the stack. It seems to be a tradition (or maybe there's a good technical reason for this) to create the main ''QApplication'' object on the stack.
+If the object is not part of a tree or is the root of a tree, then it can be created either on the heap or the stack. It seems to be a tradition (or maybe there's a good technical reason for this) to create the main ''QApplication'' object on the stack. It is also typical to create main windows (tree roots) on the stack so that they do not need to be manually deleted.
 ===== Long answer =====
@@ Line 25: / Line 25: @@
 ===== Automatic Management with Layout Managers =====
-When widgets are added to [[layout managers]], they are automatically reparented to FIXME (the layout manager's parent)|(the layout manager). Therefore, parents are not specified when creating widgets that are added to layout managers. However, you must reparent the layout manager.
+When widgets are added to [[layout managers]], they are automatically reparented to the overlying object (typically the layout manager's parent). Therefore, parents are not specified when creating widgets that are added to layout managers. However, you must reparent the layout manager itself.
 <code cpp-qt>