~oif-team/ubuntu/natty/qt4-x11/xi2.1

<td width="1">  </td><td class="postheader" valign="center"><a href="index.html"><font color="#004faf">Home</font></a> · <a href="classes.html"><font color="#004faf">All Classes</font></a> · <a href="mainclasses.html"><font color="#004faf">Main Classes</font></a> · <a href="annotated.html"><font color="#004faf">Annotated</font></a> · <a href="groups.html"><font color="#004faf">Grouped Classes</font></a> · <a href="functions.html"><font color="#004faf">Functions</font></a></td>

[Previous: <a href="qt4-scribe.html">The Scribe Classes</a>]

[<a href="qt4-intro.html">Home</a>]

[Next: <a href="qt4-designer.html">The New Qt Designer</a>]

</p>

<h1 align="center">The Qt 4 Main Window Classes</h1>

<p>Qt 4 introduces a new set of main window classes that will replace the Qt 3 main window classes, providing a more efficient implementation while remaining easy to use.</p>

<ul><li><a href="#overview-of-the-main-window-classes">Overview of the Main Window Classes</a></li>

<li><a href="#the-current-state-of-the-main-window-classes">The Current State of the Main Window Classes</a></li>

<li><a href="#what-s-changed-since-qt-4-beta-1">What's Changed Since Qt 4 Beta 1?</a></li>

<li><a href="#example-code">Example Code</a></li>

<li><a href="#what-s-changed-since-qt-3">What's Changed since Qt 3?</a></li>

</ul>

<h2>Overview of the Main Window Classes</h2>

<p>The main window-related classes have been redesigned to satisfy a number of requirements, addressing issues raised by our customers and internal developers. The aim of this redesign is to provide a more consistent and efficient framework for main window management.</p>

<p>Toolbar and dock window functionality is provided by two independent classes: <a href="qtoolbar.html">QToolBar</a> and <a href="qdockwidget.html">QDockWidget</a>. Toolbars and dock widgets reside in separate areas, with toolbars outside the dock widget area. This behavior differs from the standard Qt 3 behavior, where <a href="qtoolbar.html">QToolBar</a> inherited functionality from <a href="qdockwidget.html">QDockWidget</a>, and both types of component shared the same areas. The result is a more consistent and predictable experience for users. Toolbars and dock widgets provide feedback while being dragged into their new positions.</p>

<center><img src="images/mainwindow-docks.png" /></center><p>The diagram above shows the layout of a main window that contains both toolbars and dock widgets. Each corner area can be used by either of the adjacent dock widget areas, allowing dock widget behavior and main window layout to be specified precisely.</p>

<p>Toolbars and dock widgets are child widgets of the main window. They are no longer reparented into a dock area widget by the main window. Instead, layouts are used to manage the placement of toolbars and dock widgets. One consequence is that the old <a href="porting4.html#qdockarea">QDockArea</a> class is no longer required in Qt 4.</p>

<h2>The Current State of the Main Window Classes</h2>

<p>Qt 4 provides the following classes for managing main windows and associated user interface components:</p>

<ul>

<li><a href="qmainwindow.html">QMainWindow</a> remains the central class around which applications can be built. The interface to this class has been simplified, and much of the functionality previously included in this class is now present in the companion <a href="qdockwidget.html">QDockWidget</a> and <a href="qtoolbar.html">QToolBar</a> classes.</li>

<li><a href="qdockwidget.html">QDockWidget</a> provides a widget that can be used to create detachable tool palettes or helper windows. Dock widgets keep track of their own properties, and they can be moved, closed, and floated as external windows.</li>

<li><a href="qtoolbar.html">QToolBar</a> provides a generic toolbar widget that can hold a number of different action-related widgets, such as buttons, drop-down menus, comboboxes, and spin boxes. The emphasis on a unified action model in Qt 4 means that toolbars cooperate well with menus and keyboard shortcuts.</li>

</ul>

<h2>What's Changed Since Qt 4 Beta 1?</h2>

<ul>

<li><a href="qmainwindow.html">QMainWindow</a> and <a href="qtoolbar.html">QToolBar</a> have an <tt>iconSize</tt> property that specifies the size of the <a href="qtoolbutton.html">QToolButton</a> icons. The default size is chosen based on the style.</li>

<li>The behavior of <a href="qdockwidget.html">QDockWidget</a> has been improved significantly.</li>

</ul>

<h2>Example Code</h2>

<p>Using <a href="qmainwindow.html">QMainWindow</a> is straightforward. Generally, we subclass <a href="qmainwindow.html">QMainWindow</a> and set up menus, toolbars, and dock widgets inside the <a href="qmainwindow.html">QMainWindow</a> constructor.</p>

<p>To add a menu bar to the main window, we simply create the menus, and add them to the main window's menu bar. Note that the <a href="qmainwindow.html#menuBar">QMainWindow::menuBar</a>() function will automatically create the menu bar the first time it is called. You can also call <a href="qmainwindow.html#setMenuBar">QMainWindow::setMenuBar</a>() to use a custom menu bar in the main window.</p>

<pre>  MainWindow::MainWindow(QWidget *parent)

: QMainWindow(parent)

{

...

newAct = new QAction(tr("&New"), this);

newAct->setShortcut(tr("Ctrl+N"));

newAct->setStatusTip(tr("Create a new file"));

connect(newAct, SIGNAL(triggered()), this, SLOT(newFile()));

openAct = new QAction(tr("&Open..."), this);

openAct->setShortcut(tr("Ctrl+O"));

openAct->setStatusTip(tr("Open an existing file"));

connect(openAct, SIGNAL(triggered()), this, SLOT(open()));

...</pre>

<p>Once actions have been created, we can add them to the main window components. To begin with, we add them to the popup menus:</p>

<pre>  fileMenu = menuBar()->addMenu(tr("&File"));

fileMenu->addAction(newAct);

fileMenu->addAction(openAct);

...

fileMenu->addSeparator();

...</pre>

<p>The <a href="qtoolbar.html">QToolBar</a> and <a href="qmenu.html">QMenu</a> classes use Qt's action system to provide a consistent API. In the above code, some existing actions were added to the file menu with the <a href="qmenu.html#addAction">QMenu::addAction</a>() function. <a href="qtoolbar.html">QToolBar</a> also provides this function, making it easy to reuse actions in different parts of the main window. This avoids unnecessary duplication of work.</p>

<p>We create a toolbar as a child of the main window, and add the desired actions to it:</p>

<pre>  fileToolBar = addToolBar(tr("File"));

fileToolBar->addAction(newAct);

fileToolBar->addAction(openAct);

...</pre>

<pre>  fileToolbar->setAllowedAreas(Qt::TopToolBarArea | Qt::BottomToolBarArea);

fileToolbar->setArea(Qt::TopToolBarArea);</pre>

<p>In this example, the toolbar is restricted to the top and bottom toolbar areas of the main window, and is initially placed in the top tool bar area. We can see that the actions specified by <tt>openAction</tt> and <tt>saveAction</tt> will be displayed both on the toolbar and in the file menu.</p>

<p><a href="qdockwidget.html">QDockWidget</a> is used in a similar way to <a href="qtoolbar.html">QToolBar</a>. We create a dock widget as a child of the main window, and add widgets as children of the dock widget:</p>

<pre>  contentsWindow = new QDockWidget(tr("Table of Contents"), this);

contentsWindow->setAllowedAreas(Qt::LeftDockWidgetArea

| Qt::RightDockWidgetArea);

addDockWidget(Qt::LeftDockWidgetArea, contentsWindow);

headingList = new QListWidget(contentsWindow);

contentsWindow->setWidget(headingList);</pre>

<p>In this example, the dock widget can only be placed in the left and right dock areas, and it is initially placed in the left dock area.</p>

100

<p>The <a href="qmainwindow.html">QMainWindow</a> API allows the programmer to customize which dock widget areas occupy the four corners of the dock widget area. If required, the default can be changed with the <a href="qmainwindow.html#setCorner">QMainWindow::setCorner</a>() function:</p>

101

<pre>  setCorner(Qt::TopLeftCorner, Qt::LeftDockWidgetArea);

102

setCorner(Qt::BottomLeftCorner, Qt::LeftDockWidgetArea);

103

setCorner(Qt::TopRightCorner, Qt::RightDockWidgetArea);

104

setCorner(Qt::BottomRightCorner, Qt::RightDockWidgetArea);</pre>

105

<p>The following diagram shows the configuration produced by the above code. Note that the left and right dock widgets will occupy the top and bottom corners of the main window in this layout.</p>

106

<center><img src="images/mainwindow-docks-example.png" /></center><p>Once all of the main window components have been set up, the central widget is created and installed by using code similar to the following:</p>

107

<pre>  QWidget *centralWidget = new QWidget(this);

108

setCentralWidget(centralWidget);</pre>

109

<p>The central widget can be any subclass of <a href="qwidget.html">QWidget</a>.</p>

110

111

<h2>What's Changed since Qt 3?</h2>

112

<p>Although the <a href="qmainwindow.html">QMainWindow</a> class in Qt 3 provided support for toolbars, dock widgets, and other standard user interface components, its design meant that these items were managed through a large number of <a href="qmainwindow.html">QMainWindow</a> member functions. In Qt 4, the <a href="qmainwindow.html">QMainWindow</a> class delegates many of the management tasks to <a href="qdockwidget.html">QDockWidget</a> and <a href="qtoolbar.html">QToolBar</a>. As a result, these classes are used in a slightly different way in Qt 4.</p>

113

<p><a href="qmainwindow.html">QMainWindow</a> retains the menuBar() function, but menus are always constructed using <a href="qaction.html">QAction</a> objects. All kinds of menus are constructed using the general <a href="qmenu.html">QMenu</a> class.</p>

114

115

<pre>  QPopupMenu *fileMenu = new QPopupMenu(this);

116

openAction->addTo(fileMenu);

117

saveAction->addTo(fileMenu);

118

...

119

menuBar()->insertItem(tr("&File"), fileMenu);</pre>

120

121

<pre>  QMenu *fileMenu = menuBar()->addMenu(tr("&File"));

122

fileMenu->addAction(openAction);

123

fileMenu->addAction(saveAction);

124

...</pre>

125

<p>Toolbars follow the same pattern as menus, with the new, more consistent behavior:</p>

126

127

<pre>  QToolBar *fileTools = new QToolBar(this, "file toolbar");

128

openAction->addTo(fileTools);

129

saveAction->addTo(fileTools);

130

...</pre>

131

132

<pre>  QToolBar *fileTools = addToolBar(tr("File Tool Bar"));

133

fileTools->addAction(openAction);

134

fileTools->addAction(saveAction);

135

...</pre>

136

<p>The behavior of dock widgets is now configured through the member functions of <a href="qdockwidget.html">QDockWidget</a>. For example, compare the old and new ways of creating a dock widget in the dock area on the left hand side of the main window.</p>

137

138

<pre>  QDockWidget *dockWidget = new QDockWidget(this);

139

mainWin->moveDockWidget(dockWidget, Qt::DockLeft);</pre>

140

141

<pre>  QDockWidget *dockWidget = new QDockWidget(mainWindow);

142

mainWindow->addDockWidget(Qt::LeftDockWidgetArea, dockWidget);</pre>

143

<p>These changes provide more than a cosmetic improvement to Qt's API. They allow more consistent behavior to be defined and implemented. In response to feedback from customers, we hope to improve these classes even further.</p>

144

<p>

145

[Previous: <a href="qt4-scribe.html">The Scribe Classes</a>]

146

[<a href="qt4-intro.html">Home</a>]

147

[Next: <a href="qt4-designer.html">The New Qt Designer</a>]

148

</p>

149

150

151

152

<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>

153

154

</tr></table></div></address></body>

155

</html>

Older »