| Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions | |
The TQApplication class manages the GUI application's control flow and main settings. More...
#include <ntqapplication.h>
Inherits TQObject.
It contains the main event loop, where all events from the window system and other sources are processed and dispatched. It also handles the application's initialization and finalization, and provides session management. It also handles most system-wide and application-wide settings.
For any GUI application that uses TQt, there is precisely one TQApplication object, no matter whether the application has 0, 1, 2 or more windows at any time.
The TQApplication object is accessible through the global pointer tqApp. Its main areas of responsibility are:
The Application walk-through example contains a typical complete main() that does the usual things with TQApplication.
Since the TQApplication object does so much initialization, it must be created before any other objects related to the user interface are created.
Since it also deals with common command line arguments, it is usually a good idea to create it before any interpretation or modification of argv is done in the application itself. (Note also that for X11, setMainWidget() may change the main widget according to the -geometry option. To preserve this functionality, you must set your defaults before setMainWidget() and any overrides after.)
Non-GUI programs: While TQt is not optimized or designed for writing non-GUI programs, it's possible to use some of its classes without creating a TQApplication. This can be useful if you wish to share code between a non-GUI server and a GUI client.
See also Main Window and Related Classes.
See setColorSpec() for full details.
This enum type defines the 8-bit encoding of character string arguments to translate():
See also TQObject::tr(), TQObject::trUtf8(), and TQString::fromUtf8().
The global tqApp pointer refers to this application object. Only one application object should be created.
This application object must be constructed before any paint devices (including widgets, pixmaps, bitmaps etc.).
Note that argc and argv might be changed. TQt removes command line arguments that it recognizes. The modified argc and argv can also be accessed later with tqApp->argc() and tqApp->argv(). The documentation for argv() contains a detailed description of how to process command line arguments.
TQt debugging options (not available if TQt was compiled with the TQT_NO_DEBUG flag defined):
See Debugging Techniques for a more detailed explanation.
All TQt programs automatically support the following command line options:
The X11 version of TQt also supports some traditional X11 command line options:
Set GUIenabled to FALSE for programs without a graphical user interface that should be able to run without a window system.
On X11, the window system is initialized if GUIenabled is TRUE. If GUIenabled is FALSE, the application does not connect to the X-server. On Windows and Macintosh, currently the window system is always initialized, regardless of the value of GUIenabled. This may change in future versions of TQt.
The following example shows how to create an application that uses a graphical interface when available.
int main( int argc, char **argv )
{
#ifdef TQ_WS_X11
bool useGUI = getenv( "DISPLAY" ) != 0;
#else
bool useGUI = TRUE;
#endif
TQApplication app(argc, argv, useGUI);
if ( useGUI ) {
//start GUI version
...
} else {
//start non-GUI version
...
}
return app.exec();
}
For TQt/Embedded, passing TQApplication::GuiServer for type makes this application the server (equivalent to running with the -qws option).
Warning: TQt only supports TrueColor visuals at depths higher than 8 bits-per-pixel.
This is available only on X11.
Warning: TQt only supports TrueColor visuals at depths higher than 8 bits-per-pixel.
This is available only on X11.
This is useful for inclusion in the Help menu of an application. See the examples/menu/menu.cpp example.
This function is a convenience slot for TQMessageBox::aboutTQt().
This signal is emitted when the application is about to quit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to quit() from inside the application or when the users shuts down the entire desktop session.
The signal is particularly useful if your application has to do some last-second cleanup. Note that no user interaction is possible in this state.
See also quit().
A modal widget is a special top level widget which is a subclass of TQDialog that specifies the modal parameter of the constructor as TRUE. A modal widget must be closed before the user can continue with other parts of the program.
Modal widgets are organized in a stack. This function returns the active modal widget at the top of the stack.
See also activePopupWidget() and topLevelWidgets().
A popup widget is a special top level widget that sets the WType_Popup widget flag, e.g. the TQPopupMenu widget. When the application opens a popup widget, all events are sent to the popup. Normal widgets and modal widgets cannot be accessed before the popup widget is closed.
Only other popup widgets may be opened when a popup widget is shown. The popup widgets are organized in a stack. This function returns the active popup widget at the top of the stack.
See also activeModalWidget() and topLevelWidgets().
Returns the application top-level window that has the keyboard input focus, or 0 if no application window has the focus. Note that there might be an activeWindow() even if there is no focusWidget(), for example if no widget in that window accepts key events.
See also TQWidget::setFocus(), TQWidget::focus, and focusWidget().
Example: network/mail/smtp.cpp.
The default path list consists of a single entry, the installation directory for plugins. The default installation directory for plugins is INSTALL/plugins, where INSTALL is the directory where TQt was installed.
See also removeLibraryPath(), libraryPaths(), and setLibraryPaths().
The list is created using new and must be deleted by the caller.
The list is empty (TQPtrList::isEmpty()) if there are no widgets.
Note that some of the widgets may be hidden.
Example that updates all widgets:
TQWidgetList *list = TQApplication::allWidgets();
TQWidgetListIt it( *list ); // iterate over the widgets
TQWidget * w;
while ( (w=it.current()) != 0 ) { // for each widget...
++it;
w->update();
}
delete list; // delete the list, not the widgets
The TQWidgetList class is defined in the ntqwidgetlist.h header file.
Warning: Delete the list as soon as you have finished using it. The widgets in the list may be deleted by someone else at any time.
See also topLevelWidgets(), TQWidget::visible, and TQPtrList::isEmpty().
For example, if you have installed TQt in the C:\Trolltech\TQt directory, and you run the demo example, this function will return "C:/Trolltech/TQt/examples/demo".
On Mac OS X this will point to the directory actually containing the executable, which may be inside of an application bundle (if the application is bundled).
Warning: On Unix, this function assumes that argv[0] contains the file name of the executable (which it normally does). It also assumes that the current directory hasn't been changed by the application.
See also applicationFilePath().
For example, if you have installed TQt in the C:\Trolltech\TQt directory, and you run the demo example, this function will return "C:/Trolltech/TQt/examples/demo/demo.exe".
Warning: On Unix, this function assumes that argv[0] contains the file name of the executable (which it normally does). It also assumes that the current directory hasn't been changed by the application.
See also applicationDirPath().
Returns the number of command line arguments.
The documentation for argv() describes how to process command line arguments.
See also argv() and TQApplication::TQApplication().
Examples: chart/main.cpp and scribble/scribble.cpp.
Returns the command line argument vector.
argv()[0] is the program name, argv()[1] is the first argument and argv()[argc()-1] is the last argument.
A TQApplication object is constructed by passing argc and argv from the main() function. Some of the arguments may be recognized as TQt options and removed from the argument vector. For example, the X11 version of TQt knows about -display, -font and a few more options.
Example:
// showargs.cpp - displays program arguments in a list box
#include <ntqapplication.h>
#include <ntqlistbox.h>
int main( int argc, char **argv )
{
TQApplication a( argc, argv );
TQListBox b;
a.setMainWidget( &b );
for ( int i = 0; i < a.argc(); i++ ) // a.argc() == argc
b.insertItem( a.argv()[i] ); // a.argv()[i] == argv[i]
b.show();
return a.exec();
}
If you run showargs -display unix:0 -font 9x15bold hello world under X11, the list box contains the three strings "showargs", "hello" and "world".
TQt provides a global pointer, tqApp, that points to the TQApplication object, and through which you can access argc() and argv() in functions other than main().
See also argc() and TQApplication::TQApplication().
Examples: chart/main.cpp and scribble/scribble.cpp.
Examples: regexptester/regexptester.cpp and showimg/showimg.cpp.
This function is particularly useful for applications with many top-level windows. It could, for example, be connected to a "Quit" entry in the file menu as shown in the following code example:
// the "Quit" menu entry should try to close all windows
TQPopupMenu* file = new TQPopupMenu( this );
file->insertItem( "&Quit", tqApp, TQ_SLOT(closeAllWindows()), CTRL+Key_Q );
// when the last window is closed, the application should quit
connect( tqApp, TQ_SIGNAL( lastWindowClosed() ), tqApp, TQ_SLOT( quit() ) );
The windows are closed in random order, until one window does not accept the close event.
See also TQWidget::close(), TQWidget::closeEvent(), lastWindowClosed(), quit(), topLevelWidgets(), and TQWidget::isTopLevel.
Examples: action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, mdi/application.cpp, and qwerty/qwerty.cpp.
See also startingUp().
See also TQApplication::setColorSpec().
Example: showimg/showimg.cpp.
This function deals with session management. It is invoked when the TQSessionManager wants the application to commit all its data.
Usually this means saving all open files, after getting permission from the user. Furthermore you may want to provide a means by which the user can cancel the shutdown.
Note that you should not exit the application within this function. Instead, the session manager may or may not do this afterwards, depending on the context.
Warning: Within this function, no user interaction is possible, unless you ask the session manager sm for explicit permission. See TQSessionManager::allowsInteraction() and TQSessionManager::allowsErrorInteraction() for details and example usage.
The default implementation requests interaction and sends a close event to all visible top level widgets. If any event was rejected, the shutdown is canceled.
See also isSessionRestored(), sessionId(), saveState(), and the Session Management overview.
The default value on X11 is 1000 milliseconds. On Windows, the control panel value is used.
Widgets should not cache this value since it may be changed at any time by the user changing the global desktop settings.
See also setCursorFlashTime().
Returns TQTextCodec::codecForTr().
The desktop widget is useful for obtaining the size of the screen. It may also be possible to draw on the desktop. We recommend against assuming that it's possible to draw on the desktop, since this does not work on all operating systems.
TQDesktopWidget *d = TQApplication::desktop();
int w = d->width(); // returns desktop width
int h = d->height(); // returns desktop height
Examples: canvas/main.cpp, desktop/desktop.cpp, helpviewer/main.cpp, i18n/main.cpp, qmag/qmag.cpp, qwerty/main.cpp, and scribble/main.cpp.
See also setDesktopSettingsAware().
The default value on X11 is 400 milliseconds. On Windows, the control panel value is used.
See also setDoubleClickInterval().
This function enters the main event loop (recursively). Do not call it unless you really know what you are doing.
Use TQApplication::eventLoop()->enterLoop() instead.
To create your own instance of TQEventLoop or TQEventLoop subclass create it before you create the TQApplication object.
See also TQEventLoop.
Example: distributor/distributor.ui.h.
It is necessary to call this function to start event handling. The main event loop receives events from the window system and dispatches these to the application widgets.
Generally speaking, no user interaction can take place before calling exec(). As a special case, modal widgets like TQMessageBox can be used before calling exec(), because modal widgets call exec() to start a local event loop.
To make your application perform idle processing, i.e. executing a special function whenever there are no pending events, use a TQTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents().
See also quit(), exit(), processEvents(), and setMainWidget().
Examples: helpsystem/main.cpp, life/main.cpp, network/archivesearch/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp.
After this function has been called, the application leaves the main event loop and returns from the call to exec(). The exec() function returns retcode.
By convention, a retcode of 0 means success, and any non-zero value indicates an error.
Note that unlike the C library function of the same name, this function does return to the caller -- it is event processing that stops.
Examples: chart/chartform.cpp, extension/mainform.ui.h, and picture/picture.cpp.
This function exits from a recursive call to the main event loop. Do not call it unless you are an expert.
Use TQApplication::eventLoop()->exitLoop() instead.
If you are doing graphical changes inside a loop that does not return to the event loop on asynchronous window systems like X11 or double buffered window systems like MacOS X, and you want to visualize these changes immediately (e.g. Splash Screens), call this function.
See also flushX(), sendPostedEvents(), and TQPainter::flush().
See also syncX().
Example: xform/xform.cpp.
Returns the application widget that has the keyboard input focus, or 0 if no widget in this application has the focus.
See also TQWidget::setFocus(), TQWidget::focus, and activeWindow().
See also setFont(), fontMetrics(), and TQWidget::font.
Examples: qfd/fontdisplayer.cpp, themes/metal.cpp, and themes/themes.cpp.
See also font(), setFont(), TQWidget::fontMetrics(), and TQPainter::fontMetrics().
Returns the application's global strut.
The strut is a size object whose dimensions are the minimum that any GUI element that the user can interact with should have. For example no button should be resized to be smaller than the global strut size.
See also setGlobalStrut().
This signal is emitted after the event loop returns from a function that could block.
See also wakeUpGuiThread().
Returns TRUE if global mouse tracking is enabled; otherwise returns FALSE.
See also setGlobalMouseTracking().
Strips out vertical alignment flags and transforms an alignment align of AlignAuto into AlignLeft or AlignRight according to the language used. The other horizontal alignment flags are left untouched.
Multiple message files can be installed. Translations are searched for in the last installed message file, then the one from last, and so on, back to the first installed message file. The search stops as soon as a matching translation is found.
See also removeTranslator(), translate(), and TQTranslator::load().
Example: i18n/main.cpp.
By default, TQt will try to use the desktop settings. Call setDesktopSettingsAware(FALSE) to prevent this.
Note: All effects are disabled on screens running at less than 16-bit color depth.
See also setEffectEnabled() and TQt::UIEffect.
Returns TRUE if the application has been restored from an earlier session; otherwise returns FALSE.
See also sessionId(), commitData(), and saveState().
This signal is emitted when the user has closed the last top level window.
The signal is very useful when your application has many top level widgets but no main widget. You can then connect it to the quit() slot.
For convenience, this signal is not emitted for transient top level widgets such as popup menus and dialogs.
See also mainWidget(), topLevelWidgets(), TQWidget::isTopLevel, and TQWidget::close().
Examples: addressbook/main.cpp, extension/main.cpp, helpviewer/main.cpp, mdi/main.cpp, network/archivesearch/main.cpp, qwerty/main.cpp, and regexptester/main.cpp.
If you want to iterate over the list, you should iterate over a copy, e.g.
TQStringList list = app.libraryPaths();
TQStringList::Iterator it = list.begin();
while( it != list.end() ) {
myProcessing( *it );
++it;
}
See the plugins documentation for a description of how the library paths are used.
See also setLibraryPaths(), addLibraryPath(), removeLibraryPath(), and TQLibrary.
Lock the TQt Library Mutex. If another thread has already locked the mutex, the calling thread will block until the other thread has unlocked the mutex.
See also unlock(), locked(), and Thread Support in TQt.
Returns TRUE if the TQt Library Mutex is locked by a different thread; otherwise returns FALSE.
Warning: Due to different implementations of recursive mutexes on the supported platforms, calling this function from the same thread that previously locked the mutex will give undefined results.
See also lock(), unlock(), and Thread Support in TQt.
Returns the current loop level.
Use TQApplication::eventLoop()->loopLevel() instead.
If you create an application that inherits TQApplication and reimplement this function, you get direct access to all Carbon Events that are received from the MacOS.
Return TRUE if you want to stop the event from being processed. Return FALSE for normal event dispatching.
Returns the main application widget, or 0 if there is no main widget.
See also setMainWidget().
For certain types of events (e.g. mouse and key events), the event will be propagated to the receiver's parent and so on up to the top-level object if the receiver is not interested in the event (i.e., it returns FALSE).
There are five different ways that events can be processed; reimplementing this virtual function is just one of them. All five approaches are listed below:
See also TQObject::event() and installEventFilter().
Returns the active application override cursor.
This function returns 0 if no application cursor has been defined (i.e. the internal cursor stack is empty).
See also setOverrideCursor() and restoreOverrideCursor().
If a widget is passed in w, the default palette for the widget's class is returned. This may or may not be the application palette. In most cases there isn't a special palette for certain types of widgets, but one notable exception is the popup menu under Windows, if the user has defined a special background color for menus in the display settings.
See also setPalette() and TQWidget::palette.
Examples: desktop/desktop.cpp, themes/metal.cpp, and themes/wood.cpp.
Usually widgets call this automatically when they are polished. It may be used to do some style-based central customization of widgets.
Note that you are not limited to the public functions of TQWidget. Instead, based on meta information like TQObject::className() you are able to customize any kind of widget.
See also TQStyle::polish(), TQWidget::polish(), setPalette(), and setFont().
Note: This function is thread-safe when TQt is built withthread support.
Adds the event event with the object receiver as the receiver of the event, to an event queue and returns immediately.The event must be allocated on the heap since the post event queue will take ownership of the event and delete it once it has been posted.
When control returns to the main event loop, all events that are stored in the queue will be sent using the notify() function.
See also sendEvent() and notify().
You can call this function occasionally when your program is busy performing a long operation (e.g. copying a file).
See also exec(), TQTimer, and TQEventLoop::processEvents().
Examples: fileiconview/qfileiconview.cpp and network/ftpclient/main.cpp.
Processes pending events for maxtime milliseconds or until there are no more events to process, whichever is shorter.
You can call this function occasionally when you program is busy doing a long operation (e.g. copying a file).
See also exec(), TQTimer, and TQEventLoop::processEvents().
Waits for an event to occur, processes it, then returns.
This function is useful for adapting TQt to situations where the event processing must be grafted onto existing program loops.
Using this function in new applications may be an indication of design problems.
See also processEvents(), exec(), and TQTimer.
It's common to connect the lastWindowClosed() signal to quit(), and you also often connect e.g. TQButton::clicked() or signals in TQAction, TQPopupMenu or TQMenuBar to it.
Example:
TQPushButton *quitButton = new TQPushButton( "Quit" );
connect( quitButton, TQ_SIGNAL(clicked()), tqApp, TQ_SLOT(quit()) );
See also exit(), aboutToQuit(), lastWindowClosed(), and TQAction.
Examples: addressbook/main.cpp, mdi/main.cpp, network/archivesearch/main.cpp, regexptester/main.cpp, t2/main.cpp, t4/main.cpp, and t6/main.cpp.
This method is non-portable. It is available only in TQt/Embedded.
See also TQWSDecoration.
If you create an application that inherits TQApplication and reimplement this function, you get direct access to all TQWS (Q Window System) events that the are received from the TQWS master process.
Return TRUE if you want to stop the event from being processed. Return FALSE for normal event dispatching.
TQt/Embedded on 8-bpp displays allocates a standard 216 color cube. The remaining 40 colors may be used by setting a custom color table in the TQWS master process before any clients connect.
colorTable is an array of up to 40 custom colors. start is the starting index (0-39) and numColors is the number of colors to be set (1-40).
This method is non-portable. It is available only in TQt/Embedded.
This method is non-portable. It is available only in TQt/Embedded.
See also TQWSDecoration.
See also addLibraryPath(), libraryPaths(), and setLibraryPaths().
Note: This function is thread-safe when TQt is built withthread support.
Removes all events posted using postEvent() for receiver.The events are not dispatched, instead they are removed from the queue. You should never need to call this function. If you do call it, be aware that killing events may cause receiver to break one or more invariants.
See also installTranslator(), translate(), and TQObject::tr().
Example: i18n/main.cpp.
If setOverrideCursor() has been called twice, calling restoreOverrideCursor() will activate the first cursor set. Calling this function a second time restores the original widgets' cursors.
See also setOverrideCursor() and overrideCursor().
Examples: distributor/distributor.ui.h, network/archivesearch/archivedialog.ui.h, network/ftpclient/ftpmainwindow.ui.h, and showimg/showimg.cpp.
See also setReverseLayout().
This function deals with session management. It is invoked when the session manager wants the application to preserve its state for a future session.
For example, a text editor would create a temporary file that includes the current contents of its edit buffers, the location of the cursor and other aspects of the current editing session.
Note that you should never exit the application within this function. Instead, the session manager may or may not do this afterwards, depending on the context. Futhermore, most session managers will very likely request a saved state immediately after the application has been started. This permits the session manager to learn about the application's restart policy.
Warning: Within this function, no user interaction is possible, unless you ask the session manager sm for explicit permission. See TQSessionManager::allowsInteraction() and TQSessionManager::allowsErrorInteraction() for details.
See also isSessionRestored(), sessionId(), commitData(), and the Session Management overview.
Sends event event directly to receiver receiver, using the notify() function. Returns the value that was returned from the event handler.
The event is not deleted when the event has been sent. The normal approach is to create the event on the stack, e.g.
TQMouseEvent me( TQEvent::MouseButtonPress, pos, 0, 0 );
TQApplication::sendEvent( mainWindow, &me );
If you create the event on the heap you must delete it.
See also postEvent() and notify().
Example: popup/popup.cpp.
Note that events from the window system are not dispatched by this function, but by processEvents().
If receiver is null, the events of event_type are sent for all objects. If event_type is 0, all the events are sent for receiver.
Dispatches all posted events, i.e. empties the event queue.
Returns the current session's identifier.
If the application has been restored from an earlier session, this identifier is the same as it was in that previous session.
The session identifier is guaranteed to be unique both for different applications and for different instances of the same application.
See also isSessionRestored(), sessionKey(), commitData(), and saveState().
Returns the session key in the current session.
If the application has been restored from an earlier session, this key is the same as it was when the previous session ended.
The session key changes with every call of commitData() or saveState().
See also isSessionRestored(), sessionId(), commitData(), and saveState().
The color specification controls how the application allocates colors when run on a display with a limited amount of colors, e.g. 8 bit / 256 color displays.
The color specification must be set before you create the TQApplication object.
The options are:
Be aware that the CustomColor and ManyColor choices may lead to colormap flashing: The foreground application gets (most) of the available colors, while the background windows will look less attractive.
Example:
int main( int argc, char **argv )
{
TQApplication::setColorSpec( TQApplication::ManyColor );
TQApplication a( argc, argv );
...
}
TQColor provides more functionality for controlling color allocation and freeing up certain colors. See TQColor::enterAllocContext() for more information.
To check what mode you end up with, call TQColor::numBitPlanes() once the TQApplication object exists. A value greater than 8 (typically 16, 24 or 32) means true color.
* The color cube used by TQt has 216 colors whose red, green, and blue components always have one of the following values: 0x00, 0x33, 0x66, 0x99, 0xCC, or 0xFF.
See also colorSpec(), TQColor::numBitPlanes(), and TQColor::enterAllocContext().
Examples: helpviewer/main.cpp, opengl/main.cpp, showimg/main.cpp, t9/main.cpp, tetrax/tetrax.cpp, tetrix/tetrix.cpp, and themes/main.cpp.
Note that on Microsoft Windows, calling this function sets the cursor flash time for all windows.
See also cursorFlashTime().
This is the same as TQTextCodec::setCodecForTr().
This static function must be called before creating the TQApplication object, like this:
int main( int argc, char** argv ) {
TQApplication::setDesktopSettingsAware( FALSE ); // I know better than the user
TQApplication myApp( argc, argv ); // Use default fonts & colors
...
}
See also desktopSettingsAware().
Note that on Microsoft Windows, calling this function sets the double click interval for all windows.
See also doubleClickInterval().
Note: All effects are disabled on screens running at less than 16-bit color depth.
See also isEffectEnabled(), TQt::UIEffect, and setDesktopSettingsAware().
On application start-up, the default font depends on the window system. It can vary depending on both the window system version and the locale. This function lets you override the default font; but overriding may be a bad idea because, for example, some locales need extra-large fonts to support their special characters.
See also font(), fontMetrics(), and TQWidget::font.
Examples: desktop/desktop.cpp, themes/metal.cpp, and themes/themes.cpp.
Enabling global mouse tracking makes it possible for widget event filters or application event filters to get all mouse move events, even when no button is depressed. This is useful for special GUI elements, e.g. tooltips.
Global mouse tracking does not affect widgets and their mouseMoveEvent(). For a widget to get mouse move events when no button is depressed, it must do TQWidget::setMouseTracking(TRUE).
This function uses an internal counter. Each setGlobalMouseTracking(TRUE) must have a corresponding setGlobalMouseTracking(FALSE):
// at this point global mouse tracking is off
TQApplication::setGlobalMouseTracking( TRUE );
TQApplication::setGlobalMouseTracking( TRUE );
TQApplication::setGlobalMouseTracking( FALSE );
// at this point it's still on
TQApplication::setGlobalMouseTracking( FALSE );
// but now it's off
See also hasGlobalMouseTracking() and TQWidget::mouseTracking.
The strut is a size object whose dimensions are the minimum that any GUI element that the user can interact with should have. For example no button should be resized to be smaller than the global strut size.
The strut size should be considered when reimplementing GUI controls that may be used on touch-screens or similar IO-devices.
Example:
TQSize& WidgetClass::sizeHint() const
{
return TQSize( 80, 25 ).expandedTo( TQApplication::globalStrut() );
}
See also globalStrut().
See also libraryPaths(), addLibraryPath(), removeLibraryPath(), and TQLibrary.
In most respects the main widget is like any other widget, except that if it is closed, the application exits. Note that TQApplication does not take ownership of the mainWidget, so if you create your main widget on the heap you must delete it yourself.
You need not have a main widget; connecting lastWindowClosed() to quit() is an alternative.
For X11, this function also resizes and moves the main widget according to the -geometry command-line option, so you should set the default geometry (using TQWidget::setGeometry()) before calling setMainWidget().
See also mainWidget(), exec(), and quit().
Examples: chart/main.cpp, helpsystem/main.cpp, life/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp.
Application override cursors are intended for showing the user that the application is in a special state, for example during an operation that might take some time.
This cursor will be displayed in all the application's widgets until restoreOverrideCursor() or another setOverrideCursor() is called.
Application cursors are stored on an internal stack. setOverrideCursor() pushes the cursor onto the stack, and restoreOverrideCursor() pops the active cursor off the stack. Every setOverrideCursor() must eventually be followed by a corresponding restoreOverrideCursor(), otherwise the stack will never be emptied.
If replace is TRUE, the new cursor will replace the last override cursor (the stack keeps its depth). If replace is FALSE, the new stack is pushed onto the top of the stack.
Example:
TQApplication::setOverrideCursor( TQCursor(TQt::WaitCursor) );
calculateHugeMandelbrot(); // lunch time...
TQApplication::restoreOverrideCursor();
See also overrideCursor(), restoreOverrideCursor(), and TQWidget::cursor.
Examples: distributor/distributor.ui.h, network/archivesearch/archivedialog.ui.h, network/ftpclient/ftpmainwindow.ui.h, and showimg/showimg.cpp.
If className is passed, the change applies only to widgets that inherit className (as reported by TQObject::inherits()). If className is left 0, the change affects all widgets, thus overriding any previously set class specific palettes.
The palette may be changed according to the current GUI style in TQStyle::polish().
See also TQWidget::palette, palette(), and TQStyle::polish().
Examples: i18n/main.cpp, themes/metal.cpp, themes/themes.cpp, and themes/wood.cpp.
Changing this flag in runtime does not cause a relayout of already instantiated widgets.
See also reverseLayout().
See also startDragDistance().
See also startDragTime().
Example usage:
TQApplication::setStyle( new TQWindowsStyle );
When switching application styles, the color palette is set back to the initial colors or the system defaults. This is necessary since certain styles have to adapt the color palette to be fully style-guide compliant.
See also style(), TQStyle, setPalette(), and desktopSettingsAware().
Example: themes/themes.cpp.
Requests a TQStyle object for style from the TQStyleFactory.
The string must be one of the TQStyleFactory::keys(), typically one of "windows", "motif", "cde", "motifplus", "platinum", "sgi" and "compact". Depending on the platform, "windowsxp", "aqua" or "macintosh" may be available.
A later call to the TQApplication constructor will override the requested style when a "-style" option is passed in as a commandline parameter.
Returns 0 if an unknown style is passed, otherwise the TQStyle object returned is set as the application's GUI style.
If this number exceeds the number of visible lines in a certain widget, the widget should interpret the scroll operation as a single page up / page down operation instead.
See also wheelScrollLines().
Sets the color used to mark selections in windows style for all widgets in the application. Will repaint all widgets if the color is changed.
The default color is darkBlue.
See also winStyleHighlightColor().
For example, if the mouse position of the click is stored in startPos and the current position (e.g. in the mouse move event) is currPos, you can find out if a drag should be started with code like this:
if ( ( startPos - currPos ).manhattanLength() >
TQApplication::startDragDistance() )
startTheDrag();
TQt uses this value internally, e.g. in TQFileDialog.
The default value is 4 pixels.
See also setStartDragDistance(), startDragTime(), and TQPoint::manhattanLength().
TQt also uses this delay internally, e.g. in TQTextEdit and TQLineEdit, for starting a drag.
The default value is 500 ms.
See also setStartDragTime() and startDragDistance().
See also closingDown().
See also setStyle() and TQStyle.
See also flushX().
The list is created using new and must be deleted by the caller.
The list is empty (TQPtrList::isEmpty()) if there are no top level widgets.
Note that some of the top level widgets may be hidden, for example the tooltip if no tooltip is currently shown.
Example:
// Show all hidden top level widgets.
TQWidgetList *list = TQApplication::topLevelWidgets();
TQWidgetListIt it( *list ); // iterate over the widgets
TQWidget * w;
while ( (w=it.current()) != 0 ) { // for each top level widget...
++it;
if ( !w->isVisible() )
w->show();
}
delete list; // delete the list, not the widgets
Warning: Delete the list as soon you have finished using it. The widgets in the list may be deleted by someone else at any time.
See also allWidgets(), TQWidget::isTopLevel, TQWidget::visible, and TQPtrList::isEmpty().
Note: This function is reentrant when TQt is built with thread support.
Returns the translation text for sourceText, by querying the installed messages files. The message files are searched from the most recently installed message file back to the first installed message file.TQObject::tr() and TQObject::trUtf8() provide this functionality more conveniently.
context is typically a class name (e.g., "MyDialog") and sourceText is either English text or a short identifying text, if the output text will be very long (as for help texts).
comment is a disambiguating comment, for when the same sourceText is used in different roles within the same context. By default, it is null. encoding indicates the 8-bit encoding of character stings
See the TQTranslator documentation for more information about contexts and comments.
If none of the message files contain a translation for sourceText in context, this function returns a TQString equivalent of sourceText. The encoding of sourceText is specified by encoding; it defaults to DefaultCodec.
This function is not virtual. You can use alternative translation techniques by subclassing TQTranslator.
Warning: This method is reentrant only if all translators are installed before calling this method. Installing or removing translators while performing translations is not supported. Doing so will most likely result in crashes or other undesirable behavior.
See also TQObject::tr(), installTranslator(), and defaultCodec().
Attempts to lock the TQt Library Mutex, and returns immediately. If the lock was obtained, this function returns TRUE. If another thread has locked the mutex, this function returns FALSE, instead of waiting for the lock to become available.
The mutex must be unlocked with unlock() before another thread can successfully lock it.
See also lock(), unlock(), and Thread Support in TQt.
Unlock the TQt Library Mutex. If wakeUpGui is TRUE (the default), then the GUI thread will be woken with TQApplication::wakeUpGuiThread().
See also lock(), locked(), and Thread Support in TQt.
Wakes up the GUI thread.
See also guiThreadAwake() and Thread Support in TQt.
See also setWheelScrollLines().
If child is FALSE and there is a child widget at position (x, y), the top-level widget containing it is returned. If child is TRUE the child widget at position (x, y) is returned.
This function is normally rather slow.
See also TQCursor::pos(), TQWidget::grabMouse(), and TQWidget::grabKeyboard().
Returns a pointer to the widget at global screen position pos, or 0 if there is no TQt widget there.
If child is FALSE and there is a child widget at position pos, the top-level widget containing it is returned. If child is TRUE the child widget at position pos is returned.
The message procedure calls this function for every message received. Reimplement this function if you want to process window messages that are not processed by TQt. If you don't want the event to be processed by TQt, then return TRUE; otherwise return FALSE.
If gotFocus is TRUE, widget will become the active window. Otherwise the active window is reset to NULL.
Returns the color used to mark selections in windows style.
See also setWinStyleHighlightColor().
If you create an application that inherits TQApplication and reimplement this function, you get direct access to all X events that the are received from the X server.
Return TRUE if you want to stop the event from being processed. Return FALSE for normal event dispatching.
See also x11ProcessEvent().
It returns 1 if the event was consumed by special handling, 0 if the event was consumed by normal handling, and -1 if the event was for an unrecognized widget.
See also x11EventFilter().
Prints a warning message containing the source code file name and line number if test is FALSE.
This is really a macro defined in ntqglobal.h.
Q_ASSERT is useful for testing pre- and post-conditions.
Example:
//
// File: div.cpp
//
#include <ntqglobal.h>
int divide( int a, int b )
{
Q_ASSERT( b != 0 ); // this is line 9
return a/b;
}
If b is zero, the Q_ASSERT statement will output the following message using the tqWarning() function:
ASSERT: "b != 0" in div.cpp (9)
See also tqWarning() and Debugging.
If p is 0, prints a warning message containing the source code file name and line number, saying that the program ran out of memory.
This is really a macro defined in ntqglobal.h.
Example:
int *a;
TQ_CHECK_PTR( a = new int[80] ); // WRONG!
a = new (nothrow) int[80]; // Right
TQ_CHECK_PTR( a );
See also tqWarning() and Debugging.
Adds a global routine that will be called from the TQApplication destructor. This function is normally used to add cleanup routines for program-wide functionality.
The function given by p should take no arguments and return nothing, like this:
static int *global_ptr = 0;
static void cleanup_ptr()
{
delete [] global_ptr;
global_ptr = 0;
}
void init_ptr()
{
global_ptr = new int[100]; // allocate data
tqAddPostRoutine( cleanup_ptr ); // delete later
}
Note that for an application- or module-wide cleanup, tqAddPostRoutine() is often not suitable. People have a tendency to make such modules dynamically loaded, and then unload those modules long before the TQApplication destructor is called, for example.
For modules and libraries, using a reference-counted initialization manager or TQt' parent-child delete mechanism may be better. Here is an example of a private class which uses the parent-child mechanism to call a cleanup function at the right time:
class MyPrivateInitStuff: public TQObject {
private:
MyPrivateInitStuff( TQObject * parent ): TQObject( parent) {
// initialization goes here
}
MyPrivateInitStuff * p;
public:
static MyPrivateInitStuff * initStuff( TQObject * parent ) {
if ( !p )
p = new MyPrivateInitStuff( parent );
return p;
}
~MyPrivateInitStuff() {
// cleanup (the "post routine") goes here
}
}
By selecting the right parent widget/object, this can often be made to clean up the module's data at the exact right moment.
Prints a debug message msg, or calls the message handler (if it has been installed).
This function takes a format string and a list of arguments, similar to the C printf() function.
Example:
tqDebug( "my window handle = %x", myWidget->id() );
Under X11, the text is printed to stderr. Under Windows, the text is sent to the debugger.
Warning: The internal buffer is limited to 8196 bytes (including the '\0'-terminator).
Warning: Passing (const char *)0 as argument to tqDebug might lead to crashes on certain platforms due to the platforms printf implementation.
See also tqWarning(), tqFatal(), qInstallMsgHandler(), and Debugging.
Prints a fatal error message msg and exits, or calls the message handler (if it has been installed).
This function takes a format string and a list of arguments, similar to the C printf() function.
Example:
int divide( int a, int b )
{
if ( b == 0 ) // program error
tqFatal( "divide: cannot divide by zero" );
return a/b;
}
Under X11, the text is printed to stderr. Under Windows, the text is sent to the debugger.
Warning: The internal buffer is limited to 8196 bytes (including the '\0'-terminator).
Warning: Passing (const char *)0 as argument to tqFatal might lead to crashes on certain platforms due to the platforms printf implementation.
See also tqDebug(), tqWarning(), qInstallMsgHandler(), and Debugging.
Installs a TQt message handler h. Returns a pointer to the message handler previously defined.
The message handler is a function that prints out debug messages, warnings and fatal error messages. The TQt library (debug version) contains hundreds of warning messages that are printed when internal errors (usually invalid function arguments) occur. If you implement your own message handler, you get total control of these messages.
The default message handler prints the message to the standard output under X11 or to the debugger under Windows. If it is a fatal message, the application aborts immediately.
Only one message handler can be defined, since this is usually done on an application-wide basis to control debug output.
To restore the message handler, call qInstallMsgHandler(0).
Example:
#include <ntqapplication.h>
#include <stdio.h>
#include <stdlib.h>
void myMessageOutput( TQtMsgType type, const char *msg )
{
switch ( type ) {
case TQtDebugMsg:
fprintf( stderr, "Debug: %s\n", msg );
break;
case TQtWarningMsg:
fprintf( stderr, "Warning: %s\n", msg );
break;
case TQtFatalMsg:
fprintf( stderr, "Fatal: %s\n", msg );
abort(); // deliberately core dump
}
}
int main( int argc, char **argv )
{
qInstallMsgHandler( myMessageOutput );
TQApplication a( argc, argv );
...
return a.exec();
}
See also tqDebug(), tqWarning(), tqFatal(), and Debugging.
Obtains information about the system.
The system's word size in bits (typically 32) is returned in *wordSize. The *bigEndian is set to TRUE if this is a big-endian machine, or to FALSE if this is a little-endian machine.
In debug mode, this function calls tqFatal() with a message if the computer is truly weird (i.e. different endianness for 16 bit and 32 bit integers); in release mode it returns FALSE.
Prints the message msg and uses code to get a system specific error message. When code is -1 (the default), the system's last error code will be used if possible. Use this method to handle failures in platform specific API calls.
This function does nothing when TQt is built with TQT_NO_DEBUG defined.
Returns the TQt version number as a string, for example, "2.3.0" or "3.0.5".
The TQT_VERSION define has the numeric value in the form: 0xmmiibb (m = major, i = minor, b = bugfix). For example, TQt 3.0.5's TQT_VERSION is 0x030005.
Prints a warning message msg, or calls the message handler (if it has been installed).
This function takes a format string and a list of arguments, similar to the C printf() function.
Example:
void f( int c )
{
if ( c > 200 )
tqWarning( "f: bad argument, c == %d", c );
}
Under X11, the text is printed to stderr. Under Windows, the text is sent to the debugger.
Warning: The internal buffer is limited to 8196 bytes (including the '\0'-terminator).
Warning: Passing (const char *)0 as argument to tqWarning might lead to crashes on certain platforms due to the platforms printf implementation.
See also tqDebug(), tqFatal(), qInstallMsgHandler(), and Debugging.
This file is part of the TQt toolkit. Copyright © 1995-2007 Trolltech. All Rights Reserved.
| Copyright © 2007 Trolltech | Trademarks | TQt 3.3.8
|