source: trunk/doc/html/objecttrees.html@ 190

Last change on this file since 190 was 190, checked in by rudi, 14 years ago

reference documentation added

File size: 3.4 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/object.doc:572 -->
3<html>
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
6<title>Object Trees and Object Ownership</title>
7<style type="text/css"><!--
8fn { margin-left: 1cm; text-indent: -1cm; }
9a:link { color: #004faf; text-decoration: none }
10a:visited { color: #672967; text-decoration: none }
11body { background: #ffffff; color: black; }
12--></style>
13</head>
14<body>
15
16<table border="0" cellpadding="0" cellspacing="0" width="100%">
17<tr bgcolor="#E5E5E5">
18<td valign=center>
19 <a href="index.html">
20<font color="#004faf">Home</font></a>
21 | <a href="classes.html">
22<font color="#004faf">All&nbsp;Classes</font></a>
23 | <a href="mainclasses.html">
24<font color="#004faf">Main&nbsp;Classes</font></a>
25 | <a href="annotated.html">
26<font color="#004faf">Annotated</font></a>
27 | <a href="groups.html">
28<font color="#004faf">Grouped&nbsp;Classes</font></a>
29 | <a href="functions.html">
30<font color="#004faf">Functions</font></a>
31</td>
32<td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Object Trees and Object Ownership</h1>
33
34
35
36<p> <a href="qobject.html">QObjects</a> organize themselves in object trees.
37When you create a <a href="qobject.html">QObject</a> with another object as parent, it's added to
38the parent's <a href="qobject.html#children">children()</a> list, and
39is deleted when the parent is. It turns out that this approach fits
40the needs of GUI objects very well. For example, a <a href="qaccel.html">QAccel</a> (keyboard
41accelerator) is a child of the relevant window, so when the user closes
42that window, the accelerator is deleted too.
43<p> The static function <a href="qobject.html#objectTrees">QObject::objectTrees</a>() provides access to all
44the root objects that currently exist.
45<p> <a href="qwidget.html">QWidget</a>, the base class of everything that appears on the screen,
46extends the parent-child relationship. A child normally also becomes a
47child widget, i.e. it is displayed in its parent's coordinate system
48and is graphically clipped by its parent's boundaries. For example,
49when the an application deletes a message box after it has been
50closed, the message box's buttons and label are also deleted, just as
51we'd want, because the buttons and label are children of the message
52box.
53<p> You can also delete child objects yourself, and they will remove
54themselves from their parents. For example, when the user removes a
55toolbar it may lead to the application deleting one of its <a href="qtoolbar.html">QToolBar</a>
56objects, in which case the tool bar's <a href="qmainwindow.html">QMainWindow</a> parent would
57detect the change and reconfigure its screen space accordingly.
58<p> The debugging functions <a href="qobject.html#dumpObjectTree">QObject::dumpObjectTree</a>() and <a href="qobject.html#dumpObjectInfo">QObject::dumpObjectInfo</a>() are often useful when an application looks or
59acts strangely.
60<p>
61<!-- eof -->
62<p><address><hr><div align=center>
63<table width=100% cellspacing=0 border=0><tr>
64<td>Copyright &copy; 2007
65<a href="troll.html">Trolltech</a><td align=center><a href="trademarks.html">Trademarks</a>
66<td align=right><div align=right>Qt 3.3.8</div>
67</table></div></address></body>
68</html>
Note: See TracBrowser for help on using the repository browser.