diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2012-02-27 02:13:42 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2012-02-27 02:13:42 -0600 |
| commit | 520c05ef06ce203ad32470730f68402bc7719157 (patch) | |
| tree | 8d0bb18bbbecb4c837e232848905e5819db84b81 /doc/html/ntqapplication.html | |
| parent | b82553bf90cb5311cfe8e673b07cf6cffc95fd3c (diff) | |
| download | tqt3-520c05ef06ce203ad32470730f68402bc7719157.tar.gz tqt3-520c05ef06ce203ad32470730f68402bc7719157.zip | |
Automated update from qt3
Diffstat (limited to 'doc/html/ntqapplication.html')
| -rw-r--r-- | doc/html/ntqapplication.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/ntqapplication.html b/doc/html/ntqapplication.html index ef34d5a9b..07f5573f4 100644 --- a/doc/html/ntqapplication.html +++ b/doc/html/ntqapplication.html @@ -696,10 +696,10 @@ entry in the file menu as shown in the following code example: <p> <pre> // the "Quit" menu entry should try to close all windows <a href="ntqpopupmenu.html">TQPopupMenu</a>* file = new <a href="ntqpopupmenu.html">TQPopupMenu</a>( this ); - file-><a href="ntqmenudata.html#insertItem">insertItem</a>( "&Quit", qApp, SLOT(<a href="#closeAllWindows">closeAllWindows</a>()), CTRL+Key_Q ); + file-><a href="ntqmenudata.html#insertItem">insertItem</a>( "&Quit", tqApp, SLOT(<a href="#closeAllWindows">closeAllWindows</a>()), CTRL+Key_Q ); // when the last window is closed, the application should quit - <a href="ntqobject.html#connect">connect</a>( qApp, SIGNAL( <a href="#lastWindowClosed">lastWindowClosed</a>() ), qApp, SLOT( <a href="#quit">quit</a>() ) ); + <a href="ntqobject.html#connect">connect</a>( tqApp, SIGNAL( <a href="#lastWindowClosed">lastWindowClosed</a>() ), tqApp, SLOT( <a href="#quit">quit</a>() ) ); </pre> <p> The windows are closed in random order, until one window does not @@ -1027,8 +1027,8 @@ reimplementing this virtual function is just one of them. All five approaches are listed below: <ol type=1> <li> Reimplementing this function. This is very powerful, providing -complete control; but only one subclass can be qApp. -<p> <li> Installing an event filter on qApp. Such an event filter is able +complete control; but only one subclass can be tqApp. +<p> <li> Installing an event filter on tqApp. Such an event filter is able to process all events for all widgets, so it's just as powerful as reimplementing <a href="#notify">notify</a>(); furthermore, it's possible to have more than one application-global event filter. Global event filters even @@ -1126,7 +1126,7 @@ you also often connect e.g. <a href="ntqbutton.html#clicked">TQButton::clicked</ <p> Example: <pre> <a href="ntqpushbutton.html">TQPushButton</a> *quitButton = new <a href="ntqpushbutton.html">TQPushButton</a>( "Quit" ); - <a href="ntqobject.html#connect">connect</a>( quitButton, SIGNAL(<a href="ntqbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="#quit">quit</a>()) ); + <a href="ntqobject.html#connect">connect</a>( quitButton, SIGNAL(<a href="ntqbutton.html#clicked">clicked</a>()), tqApp, SLOT(<a href="#quit">quit</a>()) ); </pre> <p> <p>See also <a href="#exit">exit</a>(), <a href="#aboutToQuit">aboutToQuit</a>(), <a href="#lastWindowClosed">lastWindowClosed</a>(), and <a href="ntqaction.html">TQAction</a>. |