summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqmenudata.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqmenudata.3qt')
-rw-r--r--doc/man/man3/tqmenudata.3qt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/tqmenudata.3qt b/doc/man/man3/tqmenudata.3qt
index 8c092dd88..6a0d238f3 100644
--- a/doc/man/man3/tqmenudata.3qt
+++ b/doc/man/man3/tqmenudata.3qt
@@ -485,7 +485,7 @@ Ownership of \fIwidget\fR is transferred to the popup menu or to the menu bar.
.PP
Theoretically, any widget can be inserted into a popup menu. In practice, this only makes sense with certain widgets.
.PP
-If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a QLabel if you need a popup menu with a title.
+If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a TQLabel if you need a popup menu with a title.
.PP
If the widget is focus-enabled it will get focus when the user traverses the popup menu with the arrow keys. If the widget does not accept \fCArrowUp\fR and \fCArrowDown\fR in its key event handler, the focus will move back to the menu when the respective arrow key is hit one more time. This works with a QLineEdit, for example. If the widget accepts the arrow key itself, it must also provide the possibility to put the focus back on the menu again by calling TQWidget::focusNextPrevChild(). Futhermore, if the embedded widget closes the menu when the user made a selection, this can be done safely by calling:
.PP