summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqwidget.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqwidget.3qt')
-rw-r--r--doc/man/man3/tqwidget.3qt42
1 files changed, 21 insertions, 21 deletions
diff --git a/doc/man/man3/tqwidget.3qt b/doc/man/man3/tqwidget.3qt
index 9eb3ada21..5fc7aa322 100644
--- a/doc/man/man3/tqwidget.3qt
+++ b/doc/man/man3/tqwidget.3qt
@@ -13,7 +13,7 @@ TQWidget \- The base class of all user interface objects
.PP
Inherits TQObject and TQPaintDevice.
.PP
-Inherited by QButton, QFrame, QDialog, QComboBox, TQDataBrowser, TQDataView, TQDateTimeEditBase, TQDateTimeEdit, TQDesktopWidget, QDial, QDockArea, TQGLWidget, QHeader, TQMainWindow, QMotifWidget, QNPWidget, QScrollBar, TQSizeGrip, QSlider, QSpinBox, QSplashScreen, TQStatusBar, QTabBar, QTabWidget, TQWorkspace, and QXtWidget.
+Inherited by QButton, QFrame, TQDialog, TQComboBox, TQDataBrowser, TQDataView, TQDateTimeEditBase, TQDateTimeEdit, TQDesktopWidget, TQDial, QDockArea, TQGLWidget, QHeader, TQMainWindow, QMotifWidget, QNPWidget, TQScrollBar, TQSizeGrip, TQSlider, TQSpinBox, QSplashScreen, TQStatusBar, QTabBar, QTabWidget, TQWorkspace, and QXtWidget.
.PP
.SS "Public Members"
.in +1c
@@ -998,15 +998,15 @@ The TQWidget class is the base class of all user interface objects.
.PP
The widget is the atom of the user interface: it receives mouse, keyboard and other events from the window system, and paints a representation of itself on the screen. Every widget is rectangular, and they are sorted in a Z-order. A widget is clipped by its parent and by the widgets in front of it.
.PP
-A widget that isn't embedded in a parent widget is called a top-level widget. Usually, top-level widgets are windows with a frame and a title bar (although it is also possible to create top-level widgets without such decoration if suitable widget flags are used). In Qt, TQMainWindow and the various subclasses of QDialog are the most common top-level windows.
+A widget that isn't embedded in a parent widget is called a top-level widget. Usually, top-level widgets are windows with a frame and a title bar (although it is also possible to create top-level widgets without such decoration if suitable widget flags are used). In Qt, TQMainWindow and the various subclasses of TQDialog are the most common top-level windows.
.PP
A widget without a parent widget is always a top-level widget.
.PP
-Non-top-level widgets are child widgets. These are child windows in their parent widgets. You cannot usually distinguish a child widget from its parent visually. Most other widgets in TQt are useful only as child widgets. (It is possible to make, say, a button into a top-level widget, but most people prefer to put their buttons inside other widgets, e.g. QDialog.)
+Non-top-level widgets are child widgets. These are child windows in their parent widgets. You cannot usually distinguish a child widget from its parent visually. Most other widgets in TQt are useful only as child widgets. (It is possible to make, say, a button into a top-level widget, but most people prefer to put their buttons inside other widgets, e.g. TQDialog.)
.PP
If you want to use a TQWidget to hold child widgets you will probably want to add a layout to the parent TQWidget. (See Layouts.)
.PP
-TQWidget has many member functions, but some of them have little direct functionality: for example, TQWidget has a font property, but never uses this itself. There are many subclasses which provide real functionality, such as QPushButton, QListBox and QTabDialog, etc.
+TQWidget has many member functions, but some of them have little direct functionality: for example, TQWidget has a font property, but never uses this itself. There are many subclasses which provide real functionality, such as TQPushButton, QListBox and QTabDialog, etc.
.SH "Groups of functions:"
<center>.nf
.TS
@@ -1413,7 +1413,7 @@ Sometimes, you will want to reimplement this function. For example, a web browse
.PP
Child widgets call focusNextPrevChild() on their parent widgets, but only the top-level widget decides where to redirect focus. By overriding this method for an object, you thus gain control of focus traversal for all child widgets.
.PP
-\fBWarning:\fR QScrollView uses it own logic for this function, which does the right thing in most cases. But if you are using a QScrollView and want complete control of the focus chain you'll need to override QScrollView::focusNextPrevChild() and your top-level widgets' focusNextPrevChild() functions.
+\fBWarning:\fR TQScrollView uses it own logic for this function, which does the right thing in most cases. But if you are using a TQScrollView and want complete control of the focus chain you'll need to override TQScrollView::focusNextPrevChild() and your top-level widgets' focusNextPrevChild() functions.
.PP
See also focusData().
.SH "void TQWidget::focusOutEvent ( QFocusEvent * )\fC [virtual protected]\fR"
@@ -1533,7 +1533,7 @@ Hide events are sent to widgets immediately after they have been hidden.
.PP
See also event() and QHideEvent.
.PP
-Reimplemented in QScrollBar.
+Reimplemented in TQScrollBar.
.SH "const TQPixmap * TQWidget::icon () const"
Returns the widget's icon. See the "icon" property for details.
.SH "TQString TQWidget::iconText () const"
@@ -1629,7 +1629,7 @@ See also keyReleaseEvent(), QKeyEvent::ignore(), focusPolicy, focusInEvent(), fo
.PP
Example: picture/picture.cpp.
.PP
-Reimplemented in QLineEdit and TQTextEdit.
+Reimplemented in TQLineEdit and TQTextEdit.
.SH "void TQWidget::keyReleaseEvent ( QKeyEvent * e )\fC [virtual protected]\fR"
This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive key release events for the widget.
.PP
@@ -1726,7 +1726,7 @@ Returns the widget's minimum size. See the "minimumSize" property for details.
.SH "TQSize TQWidget::minimumSizeHint () const\fC [virtual]\fR"
Returns the recommended minimum size for the widget. See the "minimumSizeHint" property for details.
.PP
-Reimplemented in QLineEdit.
+Reimplemented in TQLineEdit.
.SH "int TQWidget::minimumWidth () const"
Returns the widget's minimum width. See the "minimumWidth" property for details.
.SH "void TQWidget::mouseDoubleClickEvent ( QMouseEvent * e )\fC [virtual protected]\fR"
@@ -1957,7 +1957,7 @@ Scrolls the widget including its children \fIdx\fR pixels to the right and \fIdy
.PP
After scrolling, scroll() sends a paint event for the the part that is read but not written. For example, when scrolling 10 pixels rightwards, the leftmost ten pixels of the widget need repainting. The paint event may be delivered immediately or later, depending on some heuristics (note that you might have to force processing of paint events using QApplication::sendPostedEvents() when using scroll() and move() in combination).
.PP
-See also QScrollView, erase(), and bitBlt().
+See also TQScrollView, erase(), and bitBlt().
.SH "void TQWidget::scroll ( int dx, int dy, const TQRect & r )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@@ -1965,7 +1965,7 @@ This version only scrolls \fIr\fR and does not move the children of the widget.
.PP
If \fIr\fR is empty or invalid, the result is undefined.
.PP
-See also QScrollView, erase(), and bitBlt().
+See also TQScrollView, erase(), and bitBlt().
.SH "void TQWidget::setAcceptDrops ( bool on )\fC [virtual]\fR"
Sets whether drop events are enabled for this widget to \fIon\fR. See the "acceptDrops" property for details.
.SH "void TQWidget::setActiveWindow ()\fC [virtual]\fR"
@@ -2071,7 +2071,7 @@ Sets the way the widget accepts keyboard focus. See the "focusPolicy" property f
.SH "void TQWidget::setFocusProxy ( TQWidget * w )\fC [virtual]\fR"
Sets the widget's focus proxy to widget \fIw\fR. If \fIw\fR is 0, the function resets this widget to have no focus proxy.
.PP
-Some widgets, such as QComboBox, can "have focus", but create a child widget to actually handle the focus. QComboBox, for example, creates a QLineEdit which handles the focus.
+Some widgets, such as TQComboBox, can "have focus", but create a child widget to actually handle the focus. TQComboBox, for example, creates a TQLineEdit which handles the focus.
.PP
setFocusProxy() sets the widget which will actually get focus when" this widget" gets it. If there is a focus proxy, focusPolicy(), setFocusPolicy(), setFocus() and hasFocus() all operate on the focus proxy.
.PP
@@ -2079,7 +2079,7 @@ See also focusProxy().
.SH "void TQWidget::setFont ( const TQFont & )\fC [virtual]\fR"
Sets the font currently set for the widget. See the "font" property for details.
.PP
-Reimplemented in QComboBox, TQLabel, and QTabDialog.
+Reimplemented in TQComboBox, TQLabel, and QTabDialog.
.SH "void TQWidget::setFont ( const TQFont & f, bool )"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
@@ -2101,7 +2101,7 @@ Sets enables or disables the use of input methods for this widget to \fIb\fR. Se
.SH "void TQWidget::setKeyCompression ( bool compress )\fC [virtual protected]\fR"
Enables key event compression, if \fIcompress\fR is TRUE, and disables it if \fIcompress\fR is FALSE.
.PP
-Key compression is off by default (except for QLineEdit and TQTextEdit), so widgets receive one key press event for each key press (or more, since autorepeat is usually on). If you turn it on and your program doesn't keep up with key input, TQt may try to compress key events so that more than one character can be processed in each event.
+Key compression is off by default (except for TQLineEdit and TQTextEdit), so widgets receive one key press event for each key press (or more, since autorepeat is usually on). If you turn it on and your program doesn't keep up with key input, TQt may try to compress key events so that more than one character can be processed in each event.
.PP
For example, a word processor widget might receive 2, 3 or more characters in each QKeyEvent::text(), if the layout recalculation takes too long for the CPU.
.PP
@@ -2167,7 +2167,7 @@ Sets whether mouse tracking is enabled for the widget to \fIenable\fR. See the "
.SH "void TQWidget::setPalette ( const TQPalette & )\fC [virtual]\fR"
Sets the widget's palette. See the "palette" property for details.
.PP
-Reimplemented in QComboBox, QScrollBar, and QSlider.
+Reimplemented in TQComboBox, TQScrollBar, and TQSlider.
.SH "void TQWidget::setPalette ( const TQPalette & p, bool )"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
@@ -2287,7 +2287,7 @@ See also showEvent(), hide(), showMinimized(), showMaximized(), showNormal(), vi
Examples:
.)l aclock/main.cpp, life/main.cpp, popup/popup.cpp, t1/main.cpp, t3/main.cpp, t4/main.cpp, and toplevel/options.ui.h.
.PP
-Reimplemented in QDialog and TQMenuBar.
+Reimplemented in TQDialog and TQMenuBar.
.SH "void TQWidget::showEvent ( QShowEvent * )\fC [virtual protected]\fR"
This event handler can be reimplemented in a subclass to receive widget show events.
.PP
@@ -2678,7 +2678,7 @@ This property holds whether the widget accepts keyboard focus.
.PP
Keyboard focus is initially disabled (i.e. focusPolicy() == TQWidget::NoFocus).
.PP
-You must enable keyboard focus for a widget if it processes keyboard events. This is normally done from the widget's constructor. For instance, the QLineEdit constructor calls setFocusPolicy(TQWidget::StrongFocus).
+You must enable keyboard focus for a widget if it processes keyboard events. This is normally done from the widget's constructor. For instance, the TQLineEdit constructor calls setFocusPolicy(TQWidget::StrongFocus).
.PP
See also focusPolicy, focusInEvent(), focusOutEvent(), keyPressEvent(), keyReleaseEvent(), and enabled.
.PP
@@ -2688,7 +2688,7 @@ This property holds the way the widget accepts keyboard focus.
.PP
The policy is TQWidget::TabFocus if the widget accepts keyboard focus by tabbing, TQWidget::ClickFocus if the widget accepts focus by clicking, TQWidget::StrongFocus if it accepts both, and TQWidget::NoFocus (the default) if it does not accept focus at all.
.PP
-You must enable keyboard focus for a widget if it processes keyboard events. This is normally done from the widget's constructor. For instance, the QLineEdit constructor calls setFocusPolicy(TQWidget::StrongFocus).
+You must enable keyboard focus for a widget if it processes keyboard events. This is normally done from the widget's constructor. For instance, the TQLineEdit constructor calls setFocusPolicy(TQWidget::StrongFocus).
.PP
See also focusEnabled, focusInEvent(), focusOutEvent(), keyPressEvent(), keyReleaseEvent(), and enabled.
.PP
@@ -2812,7 +2812,7 @@ This property holds whether the widget is a dialog widget.
.PP
A dialog widget is a secondary top-level widget, i.e. a top-level widget with a parent.
.PP
-See also isTopLevel and QDialog.
+See also isTopLevel and TQDialog.
.PP
Get this property's value with isDialog().
.SH "bool isModal"
@@ -2820,7 +2820,7 @@ This property holds whether the widget is a modal widget.
.PP
This property only makes sense for top-level widgets. A modal widget prevents widgets in all other top-level widgets from getting any input.
.PP
-See also isTopLevel, isDialog, and QDialog.
+See also isTopLevel, isDialog, and TQDialog.
.PP
Get this property's value with isModal().
.SH "bool isPopup"
@@ -2838,7 +2838,7 @@ A top-level widget is a widget which usually has a frame and a caption (title).
.PP
A top-level widget can have a parent widget. It will then be grouped with its parent and deleted when the parent is deleted, minimized when the parent is minimized etc. If supported by the window manager, it will also have a common taskbar entry with its parent.
.PP
-QDialog and TQMainWindow widgets are by default top-level, even if a parent widget is specified in the constructor. This behavior is specified by the WType_TopLevel widget flag.
+TQDialog and TQMainWindow widgets are by default top-level, even if a parent widget is specified in the constructor. This behavior is specified by the WType_TopLevel widget flag.
.PP
See also topLevelWidget(), isDialog, isModal, isPopup, isDesktop, and parentWidget().
.PP
@@ -3086,7 +3086,7 @@ This property holds the default layout behavior of the widget.
.PP
If there is a QLayout that manages this widget's children, the size policy specified by that layout is used. If there is no such QLayout, the result of this function is used.
.PP
-The default policy is Preferred/Preferred, which means that the widget can be freely resized, but prefers to be the size sizeHint() returns. Button-like widgets set the size policy to specify that they may stretch horizontally, but are fixed vertically. The same applies to lineedit controls (such as QLineEdit, QSpinBox or an editable QComboBox) and other horizontally orientated widgets (such as QProgressBar). TQToolButton's are normally square, so they allow growth in both directions. Widgets that support different directions (such as QSlider, QScrollBar or QHeader) specify stretching in the respective direction only. Widgets that can provide scrollbars (usually subclasses of QScrollView) tend to specify that they can use additional space, and that they can make do with less than sizeHint().
+The default policy is Preferred/Preferred, which means that the widget can be freely resized, but prefers to be the size sizeHint() returns. Button-like widgets set the size policy to specify that they may stretch horizontally, but are fixed vertically. The same applies to lineedit controls (such as TQLineEdit, TQSpinBox or an editable TQComboBox) and other horizontally orientated widgets (such as QProgressBar). TQToolButton's are normally square, so they allow growth in both directions. Widgets that support different directions (such as TQSlider, TQScrollBar or QHeader) specify stretching in the respective direction only. Widgets that can provide scrollbars (usually subclasses of TQScrollView) tend to specify that they can use additional space, and that they can make do with less than sizeHint().
.PP
See also sizeHint, QLayout, TQSizePolicy, and updateGeometry().
.PP