qt:heap_versus_stack
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
qt:heap_versus_stack [2010/12/08 22:19] – [Heap or Stack?] mithat | qt:heap_versus_stack [2010/12/08 22:59] (current) – mithat | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Heap or Stack? ====== | ====== Heap or Stack? ====== | ||
- | Should Qt objects be created on the heap or on the stack? ((Reminder: the heap is the memory store from which dynamically allocated storage is taken; the stack is used for standard variable storage as well as for passing actual parameters to functions, etc.)) | + | Should Qt objects be created on the heap or on the stack? |
===== Short answer ===== | ===== Short answer ===== | ||
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 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' | + | 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' |
===== Long answer ===== | ===== Long answer ===== | ||
Line 25: | Line 25: | ||
===== Automatic Management with Layout Managers ===== | ===== Automatic Management with Layout Managers ===== | ||
- | When widgets are added to [[layout managers]], they are automatically reparented to FIXME (the layout manager' | + | When widgets are added to [[layout managers]], they are automatically reparented to the overlying object |
<code cpp-qt> | <code cpp-qt> |
qt/heap_versus_stack.1291846745.txt.gz · Last modified: 2010/12/08 22:19 by mithat