diff options
| author | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-07-15 19:08:22 +0900 |
|---|---|---|
| committer | Michele Calgaro <michele.calgaro@yahoo.it> | 2024-07-18 09:31:41 +0900 |
| commit | a30f5359f03c3017fa19a6770fab32d25d22cb87 (patch) | |
| tree | cb365dd7a1c3666e3f972c6cad04be7b8e846cba /doc/object.doc | |
| parent | 25ad1267da6916e738a126ff5a9b41cd686adfc6 (diff) | |
| download | tqt-a30f5359.tar.gz tqt-a30f5359.zip | |
Rename graphics class nt* related files to equivalent tq* (part 1)
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc/object.doc')
| -rw-r--r-- | doc/object.doc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/object.doc b/doc/object.doc index d68d6a553..6baff9cd8 100644 --- a/doc/object.doc +++ b/doc/object.doc @@ -453,7 +453,7 @@ application program. TQt is symmetric, as usual, so you can send events in exactly the same ways as Qt's own event loop does. Most events types have special classes, most commonly \l QResizeEvent, -\l QPaintEvent, \l QMouseEvent, \l QKeyEvent and \l QCloseEvent. +\l TQPaintEvent, \l QMouseEvent, \l QKeyEvent and \l QCloseEvent. There are many others, perhaps forty or so, but most are rather odd. Each class subclasses QEvent and adds event-specific functions; see, @@ -470,7 +470,7 @@ event delivery mechanisms are flexible. The documentation for will explain enough for 99% of applications. The normal way for an event to be delivered is by calling a virtual -function. For example, \l QPaintEvent is delivered by calling \l +function. For example, \l TQPaintEvent is delivered by calling \l TQWidget::paintEvent(). This virtual function is responsible for reacting appropriately, normally by repainting the widget. If you do not perform all the necessary work in your implementation of the |