summaryrefslogtreecommitdiffstats
path: root/doc/html/qtabletevent.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/qtabletevent.html')
-rw-r--r--doc/html/qtabletevent.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/html/qtabletevent.html b/doc/html/qtabletevent.html
index 4c58e0904..850ec6bab 100644
--- a/doc/html/qtabletevent.html
+++ b/doc/html/qtabletevent.html
@@ -76,9 +76,9 @@ type of device being used with <a href="#device">device</a>() (see <a href="#Tab
whether the receiver wants the event. You should call
<a href="#accept">TQTabletEvent::accept</a>() if you handle the tablet event; otherwise
it will be sent to the parent widget.
-<p> The <a href="ntqwidget.html#setEnabled">TQWidget::setEnabled</a>() function can be used to enable or
+<p> The <a href="tqwidget.html#setEnabled">TQWidget::setEnabled</a>() function can be used to enable or
disable mouse and keyboard events for a widget.
-<p> The event handler <a href="ntqwidget.html#tabletEvent">TQWidget::tabletEvent</a>() receives all three types of tablet
+<p> The event handler <a href="tqwidget.html#tabletEvent">TQWidget::tabletEvent</a>() receives all three types of tablet
events. TQt will first send a tabletEvent and then, if it is not accepted,
it will send a mouse event. This allows applications that don't utilize
tablets to use a tablet like a mouse while also enabling those who want to