| Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions | |
The QMainWindow class provides a main application window, with a menu bar, dock windows (e.g. for toolbars), and a status bar. More...
#include <qmainwindow.h>
Inherits QWidget.
The QMainWindow class provides a main application window, with a menu bar, dock windows (e.g. for toolbars), and a status bar.
Main windows are most often used to provide menus, toolbars and a status bar around a large central widget, such as a text edit or drawing canvas. QMainWindow is usually subclassed since this makes it easier to encapsulate the central widget, menus and toolbars as well as the window's state. Subclassing makes it possible to create the slots that are called when the user clicks menu items or toolbar buttons. You can also create main windows using Qt Designer. We'll briefly review adding menu items and toolbar buttons then describe the facilities of QMainWindow itself.
QMainWindow *mw = new QMainWindow;
QTextEdit *edit = new QTextEdit( mw, "editor" );
edit->setFocus();
mw->setCaption( "Main Window" );
mw->setCentralWidget( edit );
mw->show();
QMainWindows may be created in their own right as shown above. The central widget is set with setCentralWidget(). Popup menus can be added to the default menu bar, widgets can be added to the status bar, toolbars and dock windows can be added to any of the dock areas.
ApplicationWindow * mw = new ApplicationWindow();
mw->setCaption( "Qt Example - Application" );
mw->show();
In the extract above ApplicationWindow is a subclass of QMainWindow that we must write for ourselves; this is the usual approach to using QMainWindow. (The source for the extracts in this description are taken from application/main.cpp, application/application.cpp, action/main.cpp, and action/application.cpp )
When subclassing we add the menu items and toolbars in the subclass's constructor. If we've created a QMainWindow instance directly we can add menu items and toolbars just as easily by passing the QMainWindow instance as the parent instead of the this pointer.
QPopupMenu * help = new QPopupMenu( this );
menuBar()->insertItem( "&Help", help );
help->insertItem( "&About", this, SLOT(about()), Key_F1 );
Here we've added a new menu with one menu item. The menu has been inserted into the menu bar that QMainWindow provides by default and which is accessible through the menuBar() function. The slot will be called when the menu item is clicked.
QToolBar * fileTools = new QToolBar( this, "file operations" );
fileTools->setLabel( "File Operations" );
QToolButton * fileOpen
= new QToolButton( openIcon, "Open File", QString::null,
this, SLOT(choose()), fileTools, "open file" );
This extract shows the creation of a toolbar with one toolbar button. QMainWindow supplies four dock areas for toolbars. When a toolbar is created as a child of a QMainWindow (or derived class) instance it will be placed in a dock area (the Top dock area by default). The slot will be called when the toolbar button is clicked. Any dock window can be added to a dock area either using addDockWindow(), or by creating a dock window with the QMainWindow as the parent.
e = new QTextEdit( this, "editor" );
e->setFocus();
setCentralWidget( e );
statusBar()->message( "Ready", 2000 );
Having created the menus and toolbar we create an instance of the large central widget, give it the focus and set it as the main window's central widget. In the example we've also set the status bar, accessed via the statusBar() function, to an initial message which will be displayed for two seconds. Note that you can add additional widgets to the status bar, for example labels, to show further status information. See the QStatusBar documentation for details, particularly the addWidget() function.
Often we want to synchronize a toolbar button with a menu item. For example, if the user clicks a 'bold' toolbar button we want the 'bold' menu item to be checked. This synchronization can be achieved automatically by creating actions and adding the actions to the toolbar and menu.
QAction * fileOpenAction;
fileOpenAction = new QAction( "Open File", QPixmap( fileopen ), "&Open",
CTRL+Key_O, this, "open" );
connect( fileOpenAction, SIGNAL( activated() ) , this, SLOT( choose() ) );
Here we create an action with an icon which will be used in any menu and toolbar that the action is added to. We've also given the action a menu name, '&Open', and a keyboard shortcut. The connection that we have made will be used when the user clicks either the menu item or the toolbar button.
QPopupMenu * file = new QPopupMenu( this );
menuBar()->insertItem( "&File", file );
fileOpenAction->addTo( file );
The extract above shows the creation of a popup menu. We add the menu to the QMainWindow's menu bar and add our action.
QToolBar * fileTools = new QToolBar( this, "file operations" );
fileTools->setLabel( "File Operations" );
fileOpenAction->addTo( fileTools );
Here we create a new toolbar as a child of the QMainWindow and add our action to the toolbar.
We'll now explore the functionality offered by QMainWindow.
The main window will take care of the dock areas, and the geometry of the central widget, but all other aspects of the central widget are left to you. QMainWindow automatically detects the creation of a menu bar or status bar if you specify the QMainWindow as parent, or you can use the provided menuBar() and statusBar() functions. The functions menuBar() and statusBar() create a suitable widget if one doesn't exist, and update the window's layout to make space.
QMainWindow provides a QToolTipGroup connected to the status bar. The function toolTipGroup() provides access to the default QToolTipGroup. It isn't possible to set a different tool tip group.
New dock windows and toolbars can be added to a QMainWindow using addDockWindow(). Dock windows can be moved using moveDockWindow() and removed with removeDockWindow(). QMainWindow allows default dock window (toolbar) docking in all its dock areas (top, left, right, bottom). You can use setDockEnabled() to enable and disable docking areas for dock windows. When adding or moving dock windows you can specify their 'edge' (dock area). The currently available edges are: Top, Left, Right, Bottom, Minimized (effectively a 'hidden' dock area) and TornOff (floating). See Qt::Dock for an explanation of these areas. Note that the *ToolBar functions are included for backward compatibility, all new code should use the *DockWindow functions. QToolbar is a subclass of QDockWindow so all functions that work with dock windows work on toolbars in the same way. If the user minimizes a dock window by clicking the dock window's window handle then the dock window is moved to the Minimized dock area. If the user clicks the close button, then the dock window is hidden and can only be shown again by using the dock window menu.
Some functions change the appearance of a QMainWindow globally:
The user can drag dock windows into any enabled docking area. Dock windows can also be dragged within a docking area, for example to rearrange the order of some toolbars. Dock windows can also be dragged outside any docking area (undocked or 'floated'). Being able to drag dock windows can be enabled (the default) and disabled using setDockWindowsMovable(). If the user clicks the close button on a floating dock window then the dock window will disappear. To get the dock window back the user must right click a dock area, to pop up the dock window menu, then click the name of the dock window they want to restore. Visible dock windows have a tick by their name in the dock window menu. The dock window menu is created automatically as required by createDockWindowMenu(). Since it may not always be appropriate for a dock window to appear on this menu the setAppropriate() function is used to inform the main window whether or not the dock window menu should include a particular dock window. Double clicking a dock window handle (usually on the left-hand side of the dock window) undocks (floats) the dock window. Double clicking a floating dock window's titlebar will dock the floating dock window.
The Minimized edge is a hidden dock area. If this dock area is enabled the user can hide (minimize) a dock window or show (restore) a minimized dock window by clicking the dock window handle. If the user hovers the mouse cursor over one of the handles, the caption of the dock window is displayed in a tool tip (see QDockWindow::caption() or QToolBar::label()), so if you enable the Minimized dock area, it is best to specify a meaningful caption or label for each dock window. To minimize a dock window programmatically use moveDockWindow() with an edge of Minimized.
Dock windows are moved transparently by default, i.e. during the drag an outline rectangle is drawn on the screen representing the position of the dock window as it moves. If you want the dock window to be shown normally whilst it is moved use setOpaqueMoving().
The location of a dock window, i.e. its dock area and position within the dock area, can be determined by calling getLocation(). Movable dock windows can be lined up to minimize wasted space with lineUpDockWindows(). Pointers to the dock areas are available from topDock(), leftDock(), rightDock() and bottomDock(). A customize menu item is added to the pop up dock window menu if isCustomizable() returns TRUE; it returns FALSE by default. Reimplement isCustomizable() and customize() if you want to offer this extra menu item, for example, to allow the user to change settings relating to the main window and its toolbars and dock windows.
The main window's menu bar is fixed (at the top) by default. If you want a movable menu bar, create a QMenuBar as a stretchable widget inside its own movable dock window and restrict this dock window to only live within the Top or Bottom dock:
QToolBar *tb = new QToolBar( this );
addDockWindow( tb, tr( "Menubar" ), Top, FALSE );
QMenuBar *mb = new QMenuBar( tb );
mb->setFrameStyle( QFrame::NoFrame );
tb->setStretchableWidget( mb );
setDockEnabled( tb, Left, FALSE );
setDockEnabled( tb, Right, FALSE );
An application with multiple dock windows can choose to save the current dock window layout in order to restore it later, e.g. in the next session. You can do this by using the streaming operators for QMainWindow.
To save the layout and positions of all the dock windows do this:
QFile f( filename );
if ( f.open( IO_WriteOnly ) ) {
QTextStream ts( &f );
ts << *mainWindow;
f.close();
}
To restore the dock window positions and sizes (normally when the application is next started), do following:
QFile f( filename );
if ( f.open( IO_ReadOnly ) ) {
QTextStream ts( &f );
ts >> *mainWindow;
f.close();
}
The QSettings class can be used in conjunction with the streaming operators to store the application's settings.
QMainWindow's management of dock windows and toolbars is done transparently behind-the-scenes by QDockArea.
For multi-document interfaces (MDI), use a QWorkspace as the central widget.
Adding dock windows, e.g. toolbars, to QMainWindow's dock areas is straightforward. If the supplied dock areas are not sufficient for your application we suggest that you create a QWidget subclass and add your own dock areas (see QDockArea) to the subclass since QMainWindow provides functionality specific to the standard dock areas it provides.
See also QToolBar, QDockWindow, QStatusBar, QAction, QMenuBar, QPopupMenu, QToolTipGroup, QDialog and Main Window and Related Classes.
Right-clicking a dock area will pop-up the dock window menu (createDockWindowMenu() is called automatically). When called in code you can specify what items should appear on the menu with this enum.
By default, the widget flags are set to WType_TopLevel rather than 0 as it is with QWidget. If you don't want your QMainWindow to be a top level widget then you will need to set f to 0.
If newLine is FALSE (the default) then the dockWindow is added at the end of the edge. For vertical edges the end is at the bottom, for horizontal edges (including Minimized) the end is at the right. If newLine is TRUE a new line of dock windows is started with dockWindow as the first (left-most and top-most) dock window.
If dockWindow is managed by another main window, it is first removed from that window.
Adds dockWindow to the dock area with label label.
If newLine is FALSE (the default) the dockWindow is added at the end of the edge. For vertical edges the end is at the bottom, for horizontal edges (including Minimized) the end is at the right. If newLine is TRUE a new line of dock windows is started with dockWindow as the first (left-most and top-most) dock window.
If dockWindow is managed by another main window, it is first removed from that window.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
The user is able to change the state (show or hide) a dock window that has a menu item by clicking the item.
Call setAppropriate() to indicate whether or not a particular dock window should appear on the popup menu.
See also setAppropriate().
See also topDock(), leftDock() and rightDock().
The central widget is surrounded by the left, top, right and bottom dock areas. The menu bar is above the top dock area.
See also setCentralWidget().
Example: qfd/qfd.cpp.
Reimplemented from QObject.
This function is called internally when necessary, e.g. when the user right clicks a dock area (providing isDockMenuEnabled() returns TRUE). You may reimplement this function if you wish to customize the behaviour.
The menu items representing the toolbars and dock windows are checkable. The visible dock windows are checked and the hidden dock windows are unchecked. The user can click a menu item to change its state (show or hide the dock window).
The list and the state are always kept up-to-date.
Toolbars and dock windows which are not appropriate in the current context (see setAppropriate()) are not listed in the menu.
The menu also has a menu item for lining up the dock windows.
If isCustomizable() returns TRUE, a Customize menu item is added to the menu, which if clicked will call customize(). The isCustomizable() function we provide returns FALSE and customize() does nothing, so they must be reimplemented in a subclass to be useful.
The customize menu item will only appear if isCustomizable() returns TRUE (it returns FALSE by default).
The function is intended, for example, to provide the user a means of telling the application that they wish to customize the main window, dock windows or dock areas.
The default implementation does nothing, but this may change in later Qt versions. In view of this the Customize menu item is not shown on the right-click menu by default. If you want the item to appear then reimplement isCustomizable() to return TRUE.
See also isCustomizable().
This signal is emitted when the dockWindow has changed its position. A change in position occurs when a dock window is moved within its dock area or moved to another dock area (including the Minimized and TearOff dock areas).
See also getLocation().
For example, the TornOff dock area may contain closed dock windows but these are returned along with the visible dock windows.
Returns the list of dock windows which belong to this main window, regardless of which dock area they are in or what their state is, (e.g. irrespective of whether they are visible or not).
Returns TRUE if the dock windows are movable; otherwise returns FALSE. See the "dockWindowsMovable" property for details.
If the dw dock window is found in the main window the function returns TRUE and populates the dock variable with the dw's dock area and the index with the dw's position within the dock area. It also sets nl to TRUE if the dw begins a new line (otherwise FALSE), and extraOffset with the dw's offset.
If the dw dock window is not found then the function returns FALSE and the state of dock, index, nl and extraOffset is undefined.
If you want to save and restore dock window positions then use operator>>() and operator<<().
See also operator>>() and operator<<().
See also customize().
See also setDockEnabled().
Returns TRUE if area is enabled, i.e. it can accept user dragged dock windows; otherwise returns FALSE.
See also setDockEnabled().
Returns TRUE if dock is enabled for the dock window tb, otherwise returns FALSE.
See also setDockEnabled().
Returns TRUE if area is enabled for the dock window dw, otherwise returns FALSE.
See also setDockEnabled().
Returns TRUE, if the dock window menu is enabled; otherwise returns FALSE.
The menu lists the (appropriate()) dock windows (which may be shown or hidden), and has a "Line Up Dock Windows" menu item. It will also have a "Customize" menu item if isCustomizable() returns TRUE.
See also setDockEnabled(), lineUpDockWindows(), appropriate() and setAppropriate().
See also rightDock(), topDock() and bottomDock().
If keepNewLines is TRUE, all dock windows stay on their original lines. If keepNewLines is FALSE then newlines may be removed to achieve the most compact layout possible.
The method only works if dockWindowsMovable() returns TRUE.
If you want to do small adjustments to the menu, you can do it in this slot. Else reimplement createDockWindowMenu().
If there isn't one, then menuBar() creates an empty menu bar.
See also statusBar().
For vertical edges the end is at the bottom, for horizontal edges (including Minimized) the end is at the right.
If dockWindow is managed by another main window, it is first removed from that window.
Moves dockWindow to position index of edge.
Any dock windows with positions index or higher have their position number incremented and any of these on the same line are moved right (down for vertical dock areas) to make room.
If nl is TRUE, a new dock window line is created below the line in which the moved dock window appears and the moved dock window, with any others with higher positions on the same line, is moved to this new line.
The extraOffset is the space to put between the left side of the dock area (top side for vertical dock areas) and the dock window. (This is mostly used for restoring dock windows to the positions the user has dragged them to.)
If dockWindow is managed by another main window, it is first removed from that window.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
Returns TRUE if dock windows are moved opaquely; otherwise returns FALSE. See the "opaqueMoving" property for details.
This signal is called whenever the setUsesBigPixmaps() is called with a value different to the current setting. All widgets that should respond to such changes, e.g. toolbar buttons, must connect to this signal.
See also leftDock(), topDock() and bottomDock().
Returns TRUE if the main window right-justifies its dock windows; otherwise returns FALSE. See the "rightJustification" property for details.
If a is TRUE then the dw will appear as a menu item on the dock window menu. The user is able to change the state (show or hide) a dock window that has a menu item by clicking the item; depending on the state of your application, this may or may not be appropriate. If a is FALSE the dw will not appear on the popup menu.
See also showDockMenu(), isCustomizable() and customize().
The central widget is surrounded by the left, top, right and bottom dock areas. The menu bar is above the top dock area.
See also centralWidget().
Users can dock (drag) dock windows into any enabled dock area.
If enable is TRUE then users can dock the dw dock window in the dock area. If enable is FALSE users cannot dock the dw dock window in the dock area.
In general users can dock (drag) dock windows into any enabled dock area. Using this function particular dock areas can be enabled (or disabled) as docking points for particular dock windows.
The menu lists the (appropriate()) dock windows (which may be shown or hidden), and has a line up dock window item. It will also have a Customize menu item if isCustomizable() returns TRUE.
See also lineUpDockWindows() and isDockMenuEnabled().
Sets whether the dock windows are movable. See the "dockWindowsMovable" property for details.
Sets whether dock windows are moved opaquely. See the "opaqueMoving" property for details.
Sets whether the main window right-justifies its dock windows. See the "rightJustification" property for details.
Sets whether big pixmaps are enabled. See the "usesBigPixmaps" property for details.
Sets whether text labels for toolbar buttons are enabled. See the "usesTextLabel" property for details.
The default implementation uses the dock window menu which gets created by createDockWindowMenu(). You can reimplement createDockWindowMenu() if you want to use your own specialized popup menu.
See also menuBar() and toolTipGroup().
Example: qfd/qfd.cpp.
For example, the TornOff dock area may contain closed toolbars but these are returned along with the visible toolbars.
See also dockWindows().
See also menuBar() and statusBar().
See also bottomDock(), leftDock() and rightDock().
Returns TRUE if big pixmaps are enabled; otherwise returns FALSE. See the "usesBigPixmaps" property for details.
Returns TRUE if text labels for toolbar buttons are enabled; otherwise returns FALSE. See the "usesTextLabel" property for details.
This signal is called whenever the setUsesTextLabel() is called with a value different to the current setting. All widgets that should respond to such changes, e.g. toolbar buttons, must connect to this signal.
This is the same as QWhatsThis::enterWhatsThisMode(), but implemented as a main window object's slot. This way it can easily be used for popup menus, for example:
QPopupMenu * help = new QPopupMenu( this );
help->insertItem( "What's &This", this , SLOT(whatsThis()), SHIFT+Key_F1);
See also QWhatsThis::enterWhatsThisMode().
This property holds whether the dock windows are movable.
If TRUE (the default), the user will be able to move Movable dock windows from one QMainWindow dock area to another, including the TearOff area (i.e. where the dock window floats freely as a window in its own right), and the Minimized area (where only the dock window's handle is shown below the menu bar). Moveable dock windows can also be moved within QMainWindow dock areas, i.e. to rearrange them within a dock area.
If FALSE the user will not be able to move any dock windows.
By default dock windows are moved transparently (i.e. only an outline rectangle is shown during the drag), but this setting can be changed with setOpaqueMoving().
See also setDockEnabled() and opaqueMoving.
Set this property's value with setDockWindowsMovable() and get this property's value with dockWindowsMovable().
This property holds whether dock windows are moved opaquely.
If TRUE the dock windows of the main window are shown opaquely (i.e. it shows the toolbar as it looks when docked) when moved. If FALSE (the default) they are shown transparently, (i.e. as an outline rectangle).
Opaque moving of toolbars and dockwindows is known to have several problems. We suggest not to use it at this point in time. We will fix that behavior problems in a future release.
Set this property's value with setOpaqueMoving() and get this property's value with opaqueMoving().
This property holds whether the main window right-justifies its dock windows.
If disabled (the default), stretchable dock windows are expanded, and non-stretchable dock windows are given the minimum space they need. Since most dock windows are not stretchable, this usually results in a unjustified right edge (or unjustified bottom edge for a vertical dock area). If enabled, the main window will right-justify its dock windows.
See also QDockWindow::setVerticalStretchable() and QDockWindow::setHorizontalStretchable().
Set this property's value with setRightJustification() and get this property's value with rightJustification().
This property holds whether big pixmaps are enabled.
If FALSE (the default), the tool buttons will use small pixmaps; otherwise big pixmaps will be used.
Tool buttons and other widgets that wish to respond to this setting are responsible for reading the correct state on startup, and for connecting to the main window's widget's pixmapSizeChanged() signal.
Set this property's value with setUsesBigPixmaps() and get this property's value with usesBigPixmaps().
This property holds whether text labels for toolbar buttons are enabled.
If disabled (the default), the tool buttons will not use text labels. If enabled, text labels will be used.
Tool buttons and other widgets that wish to respond to this setting are responsible for reading the correct state on startup, and for connecting to the main window's widget's usesTextLabelChanged() signal.
See also QToolButton::usesTextLabel.
Set this property's value with setUsesTextLabel() and get this property's value with usesTextLabel().
Writes the layout (sizes and positions) of the dock windows in the dock areas of the QMainWindow mainWindow, including Minimized and TornOff dock windows, to the text stream ts.
This can be used, for example, in conjunction with QSettings to save the user's layout.
See also operator>>().
Reads the layout (sizes and positions) of the dock windows in the dock areas of the QMainWindow mainWindow from the text stream, ts, including Minimized and TornOff dock windows. Restores the dock windows and dock areas to these sizes and positions. The layout information must be in the format produced by operator<<().
This can be used, for example, in conjunction with QSettings to restore the user's layout.
See also operator<<().
This file is part of the Qt toolkit. Copyright © 1995-2002 Trolltech. All Rights Reserved.
| Copyright © 2002 Trolltech | Trademarks | Qt version 3.0.4
|