Main windows are most often used to provide menus, toolbars and a status bar around a large central widget, such as a text edit, drawing canvas or TQWorkspace (for MDI applications). TQMainWindow 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 TQt Designer. We'll briefly review adding menu items and toolbar buttons then describe the facilities of TQMainWindow itself.
TQMainWindows 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.
In the extract above ApplicationWindow is a subclass of TQMainWindow that we must write for ourselves; this is the usual approach to using TQMainWindow. (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 TQMainWindow instance directly we can add menu items and toolbars just as easily by passing the TQMainWindow instance as the parent instead of the \fIthis\fR pointer.
Here we've added a new menu with one menu item. The menu has been inserted into the menu bar that TQMainWindow provides by default and which is accessible through the menuBar() function. The slot will be called when the menu item is clicked.
This extract shows the creation of a toolbar with one toolbar button. TQMainWindow supplies four dock areas for toolbars. When a toolbar is created as a child of a TQMainWindow (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 TQMainWindow as the parent.
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 TQStatusBar 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.
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 \fIor\fR the toolbar button.
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. TQMainWindow automatically detects the creation of a menu bar or status bar if you specify the TQMainWindow 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.
TQMainWindow provides a TQToolTipGroup connected to the status bar. The function toolTipGroup() provides access to the default TQToolTipGroup. It isn't possible to set a different tool tip group.
New dock windows and toolbars can be added to a TQMainWindow using addDockWindow(). Dock windows can be moved using moveDockWindow() and removed with removeDockWindow(). TQMainWindow 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 TQt::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. TQToolbar is a subclass of QDockWindow so all functions that work with dock windows work on toolbars in the same way.
If the user clicks the close button, then the dock window is hidden. A dock window can be hidden or unhidden by the user by right clicking a dock area and clicking the name of the relevant dock window on the pop up dock window menu. This menu lists the names of every dock window; visible dock windows have a tick beside their names. 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. (See also TQMainWindow::DockWindows.)
The user can drag dock windows into any enabled docking area. Dock windows can also be dragged \fIwithin\fR 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().
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 TQToolBar::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().
.PP
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 TQMenuBar as a stretchable widget inside its own movable dock window and restrict this dock window to only live within the Top or Bottom dock:
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 TQMainWindow.
Adding dock windows, e.g. toolbars, to TQMainWindow's dock areas is straightforward. If the supplied dock areas are not sufficient for your application we suggest that you create a TQWidget subclass and add your own dock areas (see QDockArea) to the subclass since TQMainWindow provides functionality specific to the standard dock areas it provides.
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 they are with TQWidget. If you don't want your TQMainWindow to be a top level widget then you will need to set \fIf\fR to 0.
Adds \fIdockWindow\fR to the \fIedge\fR dock area.
.PP
If \fInewLine\fR is FALSE (the default) then the \fIdockWindow\fR is added at the end of the \fIedge\fR. For vertical edges the end is at the bottom, for horizontal edges (including Minimized) the end is at the right. If \fInewLine\fR is TRUE a new line of dock windows is started with \fIdockWindow\fR as the first (left-most and top-most) dock window.
.PP
If \fIdockWindow\fR 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.
.PP
Adds \fIdockWindow\fR to the dock area with label \fIlabel\fR.
.PP
If \fInewLine\fR is FALSE (the default) the \fIdockWindow\fR is added at the end of the \fIedge\fR. For vertical edges the end is at the bottom, for horizontal edges (including Minimized) the end is at the right. If \fInewLine\fR is TRUE a new line of dock windows is started with \fIdockWindow\fR as the first (left-most and top-most) dock window.
.PP
If \fIdockWindow\fR is managed by another main window, it is first removed from that window.
Creates the dock window menu which contains all toolbars (if \fIdockWindows\fR is OnlyToolBars ), all dock windows (if \fIdockWindows\fR is NoToolBars) or all toolbars and dock windows (if \fIdockWindows\fR is AllDockWindows - the default).
.PP
This function is called internally when necessary, e.g. when the user right clicks a dock area (providing isDockMenuEnabled() returns TRUE).
.PP
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).
.PP
The list and the state are always kept up-to-date.
.PP
Toolbars and dock windows which are not appropriate in the current context (see setAppropriate()) are not listed in the menu.
.PP
The menu also has a menu item for lining up the dock windows.
.PP
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.
This function is called when the user clicks the Customize menu item on the dock window menu.
.PP
The customize menu item will only appear if isCustomizable() returns TRUE (it returns FALSE by default).
.PP
The function is intended, for example, to provide the user with a means of telling the application that they wish to customize the main window, dock windows or dock areas.
.PP
The default implementation does nothing and 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, and reimplement this function to do whatever you want.
This signal is emitted when the \fIdockWindow\fR 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 \fCTearOff\fR dock areas).
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
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).
If the \fIdw\fR dock window is found in the main window the function returns TRUE and populates the \fIdock\fR variable with the dw's dock area and the \fIindex\fR with the dw's position within the dock area. It also sets \fInl\fR to TRUE if the \fIdw\fR begins a new line (otherwise FALSE), and \fIextraOffset\fR with the dock window's offset.
.PP
If the \fIdw\fR dock window is not found then the function returns FALSE and the state of \fIdock\fR, \fIindex\fR, \fInl\fR and \fIextraOffset\fR is undefined.
.PP
If you want to save and restore dock window positions then use operator>>() and operator<<().
Returns TRUE if the dock area dock window menu includes the Customize menu item (which calls customize() when clicked). Returns FALSE by default, i.e. the popup menu will not contain a Customize menu item. You will need to reimplement this function and set it to return TRUE if you wish the user to be able to see the dock window menu.
Returns TRUE, if the dock window menu is enabled; otherwise returns FALSE.
.PP
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.
.PP
See also setDockEnabled(), lineUpDockWindows(), appropriate(), and setAppropriate().
This function will line up dock windows within the visible dock areas (Top, Left, Right and Bottom) as compactly as possible.
.PP
If \fIkeepNewLines\fR is TRUE, all dock windows stay on their original lines. If \fIkeepNewLines\fR is FALSE then newlines may be removed to achieve the most compact layout possible.
.PP
The method only works if dockWindowsMovable() returns TRUE.
This slot is called from the aboutToShow() signal of the default dock menu of the mainwindow. The default implementation initializes the menu with all dock windows and toolbars in this slot.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Moves \fIdockWindow\fR to position \fIindex\fR within the \fIedge\fR dock area.
.PP
Any dock windows with positions \fIindex\fR 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.
.PP
If \fInl\fR 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.
.PP
The \fIextraOffset\fR 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.)
.PP
If \fIdockWindow\fR is managed by another main window, it is first removed from that window.
This signal is emitted 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.
Use this function to control whether or not the \fIdw\fR dock window's caption should appear as a menu item on the dock window menu that lists the dock windows.
.PP
If \fIa\fR is TRUE then the \fIdw\fR 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 \fIa\fR is FALSE the \fIdw\fR will not appear on the popup menu.
.PP
See also showDockMenu(), isCustomizable(), and customize().
If \fIenable\fR is TRUE then users can dock windows in the \fIdock\fR area. If \fIenable\fR is FALSE users cannot dock windows in the \fIdock\fR dock area.
.PP
Users can dock (drag) dock windows into any enabled dock area.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
If \fIenable\fR is TRUE then users can dock the \fIdw\fR dock window in the \fIdock\fR area. If \fIenable\fR is FALSE users cannot dock the \fIdw\fR dock window in the \fIdock\fR area.
.PP
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.
If \fIb\fR is TRUE, then right clicking on a dock window or dock area will pop up the dock window menu. If \fIb\fR is FALSE, right clicking a dock window or dock area will not pop up the menu.
.PP
The menu lists the (appropriate()) dock windows (which may be shown or hidden), and has a "Line Up Dock Windows" item. It will also have a "Customize" menu item if isCustomizable() returns TRUE.
.PP
See also lineUpDockWindows() and isDockMenuEnabled().
Shows the dock menu at the position \fIglobalPos\fR. The menu lists the dock windows so that they can be shown (or hidden), lined up, and possibly customized. Returns TRUE if the menu is shown; otherwise returns FALSE.
.PP
If you want a custom menu, reimplement this function. You can create the menu from scratch or call createDockWindowMenu() and modify the result.
This signal is emitted 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.
Enters 'What's This?' mode and returns immediately.
.PP
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:
If TRUE (the default), the user will be able to move movable dock windows from one TQMainWindow dock area to another, including the \fCTearOff\fR 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 TQMainWindow dock areas, i.e. to rearrange them within a dock area.
If FALSE the user will not be able to move any dock windows.
.PP
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().
.PP
See also setDockEnabled() and opaqueMoving.
.PP
Set this property's value with setDockWindowsMovable() and get this property's value with dockWindowsMovable().
.SH "bool opaqueMoving"
This property holds whether dock windows are moved opaquely.
.PP
If TRUE the dock windows of the main window are shown opaquely (i.e. it shows the toolbar as it looks when docked) whilst it is being moved. If FALSE (the default) they are shown transparently, (i.e. as an outline rectangle).
.PP
\fBWarning:\fR Opaque moving of toolbars and dockwindows is known to have several problems. We recommend avoiding the use of this feature for the time being. We intend fixing the problems in a future release.
.PP
Set this property's value with setOpaqueMoving() and get this property's value with opaqueMoving().
.SH "bool rightJustification"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
This property holds whether the main window right-justifies its dock windows.
.PP
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 an unjustified right edge (or unjustified bottom edge for a vertical dock area). If enabled, the main window will right-justify its dock windows.
.PP
See also QDockWindow::setVerticalStretchable() and QDockWindow::setHorizontalStretchable().
.PP
Set this property's value with setRightJustification() and get this property's value with rightJustification().
.SH "bool usesBigPixmaps"
This property holds whether big pixmaps are enabled.
.PP
If FALSE (the default), the tool buttons will use small pixmaps; otherwise big pixmaps will be used.
.PP
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.
.PP
Set this property's value with setUsesBigPixmaps() and get this property's value with usesBigPixmaps().
.SH "bool usesTextLabel"
This property holds whether text labels for toolbar buttons are enabled.
.PP
If disabled (the default), the tool buttons will not use text labels. If enabled, text labels will be used.
.PP
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.
Writes the layout (sizes and positions) of the dock windows in the dock areas of the TQMainWindow \fImainWindow\fR, including Minimized and TornOff dock windows, to the text stream \fIts\fR.
Reads the layout (sizes and positions) of the dock windows in the dock areas of the TQMainWindow \fImainWindow\fR from the text stream, \fIts\fR, 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<<().
