<trbgcolor=#f0f0f0><td><b><ahref="tqdatetimeedit.html">TQDateTimeEdit</a></b><td>Combines a TQDateEdit and TQTimeEdit widget into a single widget for editing datetimes
<trbgcolor=#f0f0f0><td><b><ahref="ntqdesktopwidget.html">TQDesktopWidget</a></b><td>Access to screen information on multi-head systems
<trbgcolor=#f0f0f0><td><b><ahref="tqdesktopwidget.html">TQDesktopWidget</a></b><td>Access to screen information on multi-head systems
<trbgcolor=#f0f0f0><td><b><ahref="ntqheader.html">TQHeader</a></b><td>Header row or column, e.g. for tables and listviews
<trbgcolor=#f0f0f0><td><b><ahref="tqiconfactory.html">TQIconFactory</a></b><td>Used to create pixmaps for a TQIconSet
<trbgcolor=#f0f0f0><td><b><ahref="tqiconview.html">TQIconView</a></b><td>Area with movable labelled icons
<trbgcolor=#f0f0f0><td><b><ahref="tqdatetimeedit.html">TQDateTimeEdit</a></b><td>Combines a TQDateEdit and TQTimeEdit widget into a single widget for editing datetimes
<trbgcolor=#f0f0f0><td><b><ahref="tqdatetimeeditbase.html">TQDateTimeEditBase</a></b><td>Abstraction for date and edit editors
<trbgcolor=#f0f0f0><td><b><ahref="tqdeepcopy.html">TQDeepCopy</a></b><td>Template class which ensures that <ahref="shclass.html#implicitly-shared">implicitly shared</a> and <ahref="shclass.html#explicitly-shared">explicitly shared</a> classes reference unique data
<trbgcolor=#f0f0f0><td><b><ahref="ntqdesktopwidget.html">TQDesktopWidget</a></b><td>Access to screen information on multi-head systems
<trbgcolor=#f0f0f0><td><b><ahref="tqdesktopwidget.html">TQDesktopWidget</a></b><td>Access to screen information on multi-head systems
<trbgcolor=#f0f0f0><td><b><ahref="ntqdial.html">TQDial</a></b><td>Rounded range control (like a speedometer or potentiometer)
<trbgcolor=#f0f0f0><td><b><ahref="ntqdialog.html">TQDialog</a></b><td>The base class of dialog windows
<trbgcolor=#f0f0f0><td><b><ahref="tqdict.html">TQDict</a></b><td>Template class that provides a dictionary based on TQString keys
<trbgcolor=#f0f0f0><td><b><ahref="tqtoolbutton.html">TQToolButton</a></b><td>Quick-access button to commands or options, usually used inside a TQToolBar
<trbgcolor=#f0f0f0><td><b><ahref="tqtooltip.html">TQToolTip</a></b><td>Tool tips (balloon help) for any widget or rectangular part of a widget
<trbgcolor=#f0f0f0><td><b><ahref="tqtooltipgroup.html">TQToolTipGroup</a></b><td>Collects tool tips into related groups
<trbgcolor=#f0f0f0><td><b><ahref="ntqtranslator.html">TQTranslator</a></b><td><ahref="i18n.html#internationalization">Internationalization</a> support for text output
<trbgcolor=#f0f0f0><td><b><ahref="qtranslatormessage.html">TQTranslatorMessage</a></b><td>Translator message and its properties
<trbgcolor=#f0f0f0><td><b><ahref="tqtranslator.html">TQTranslator</a></b><td><ahref="i18n.html#internationalization">Internationalization</a> support for text output
<trbgcolor=#f0f0f0><td><b><ahref="tqtranslatormessage.html">TQTranslatorMessage</a></b><td>Translator message and its properties
<trbgcolor=#f0f0f0><td><b><ahref="tqtsciicodec.html">TQTsciiCodec</a></b><td>Conversion to and from the Tamil TSCII encoding
<trbgcolor=#f0f0f0><td><b><ahref="tquridrag.html">TQUriDrag</a></b><td>Drag object for a list of URI references
<trbgcolor=#f0f0f0><td><b><ahref="tqurl.html">TQUrl</a></b><td>URL parser and simplifies working with URLs
<trbgcolor=#f0f0f0><td><b><ahref="ntqapplication.html">TQApplication</a></b><td>Manages the GUI application's control flow and main settings
<trbgcolor=#f0f0f0><td><b><ahref="ntqdockarea.html">TQDockArea</a></b><td>Manages and lays out TQDockWindows
<trbgcolor=#f0f0f0><td><b><ahref="ntqdockwindow.html">TQDockWindow</a></b><td>Widget which can be docked inside a TQDockArea or floated as a top level window on the desktop
<trbgcolor=#f0f0f0><td><b><ahref="ntqeventloop.html">TQEventLoop</a></b><td>Manages the event queue
<trbgcolor=#f0f0f0><td><b><ahref="tqeventloop.html">TQEventLoop</a></b><td>Manages the event queue
<trbgcolor=#f0f0f0><td><b><ahref="tqmainwindow.html">TQMainWindow</a></b><td>Main application window, with a menu bar, dock windows (e.g. for toolbars), and a status bar
<trbgcolor=#f0f0f0><td><b><ahref="tqmenubar.html">TQMenuBar</a></b><td>Horizontal menu bar
<trbgcolor=#f0f0f0><td><b><ahref="tqpopupmenu.html">TQPopupMenu</a></b><td>Popup menu widget
@ -45,8 +45,8 @@ and <a href="signalsandslots.html">Signals and Slots</a>.
<trbgcolor=#f0f0f0><td><b><ahref="tqdragleaveevent.html">TQDragLeaveEvent</a></b><td>Event which is sent to the widget when a drag and drop leaves the widget
<trbgcolor=#f0f0f0><td><b><ahref="tqdragmoveevent.html">TQDragMoveEvent</a></b><td>Event which is sent while a drag and drop is in progress
<trbgcolor=#f0f0f0><td><b><ahref="tqdropevent.html">TQDropEvent</a></b><td>Event which is sent when a drag and drop is completed
<trbgcolor=#f0f0f0><td><b><ahref="ntqevent.html">TQEvent</a></b><td>The base class of all event classes. Event objects contain event parameters
<trbgcolor=#f0f0f0><td><b><ahref="ntqeventloop.html">TQEventLoop</a></b><td>Manages the event queue
<trbgcolor=#f0f0f0><td><b><ahref="tqevent.html">TQEvent</a></b><td>The base class of all event classes. Event objects contain event parameters
<trbgcolor=#f0f0f0><td><b><ahref="tqeventloop.html">TQEventLoop</a></b><td>Manages the event queue
<trbgcolor=#f0f0f0><td><b><ahref="qfocusevent.html">TQFocusEvent</a></b><td>Event parameters for widget focus events
<trbgcolor=#f0f0f0><td><b><ahref="qhideevent.html">TQHideEvent</a></b><td>Event which is sent after a widget is hidden
<trbgcolor=#f0f0f0><td><b><ahref="tqicondragevent.html">TQIconDragEvent</a></b><td>Signals that a main icon drag has begun
<p> In TQt, an event is an object that inherits <ahref="ntqevent.html">TQEvent</a>. Events are
<p> In TQt, an event is an object that inherits <ahref="tqevent.html">TQEvent</a>. Events are
delivered to objects that inherit <ahref="tqobject.html">TQObject</a> through calling <ahref="tqobject.html#event">TQObject::event</a>(). Event delivery means that an event has occurred, the
<ahref="ntqevent.html">TQEvent</a> indicates precisely what, and the <ahref="tqobject.html">TQObject</a> needs to respond. Most
<ahref="tqevent.html">TQEvent</a> indicates precisely what, and the <ahref="tqobject.html">TQObject</a> needs to respond. Most
events are specific to <ahref="tqwidget.html">TQWidget</a> and its subclasses, but there are
important events that aren't related to graphics, for example, socket
activation, which is the event used by <ahref="tqsocketnotifier.html">TQSocketNotifier</a> for its
@ -47,7 +47,7 @@ events in exactly the same ways as TQt's own event loop does.
<p> Most events types have special classes, most commonly <ahref="qresizeevent.html">TQResizeEvent</a>,
<ahref="tqpaintevent.html">TQPaintEvent</a>, <ahref="qmouseevent.html">TQMouseEvent</a>, <ahref="qkeyevent.html">TQKeyEvent</a> and <ahref="qcloseevent.html">TQCloseEvent</a>.
There are many others, perhaps forty or so, but most are rather odd.
<p> Each class subclasses <ahref="ntqevent.html">TQEvent</a> and adds event-specific functions; see,
<p> Each class subclasses <ahref="tqevent.html">TQEvent</a> and adds event-specific functions; see,
for example, <ahref="qresizeevent.html">TQResizeEvent</a>. In the case of <ahref="qresizeevent.html">TQResizeEvent</a>, <ahref="qresizeevent.html#size">TQResizeEvent::size</a>() and <ahref="qresizeevent.html#oldSize">TQResizeEvent::oldSize</a>() are added.
<p> Some classes support more than one event type. <ahref="qmouseevent.html">TQMouseEvent</a>
@ -345,7 +345,7 @@ project file as a command-line argument.
Norwegian and Swedish. If you use <ahref="qmake-manual.html">qmake</a>, you usually don't need an extra project
file for <em>lupdate</em>; your <tt>qmake</tt> project file will work fine once
you add the <tt>TRANSLATIONS</tt> entry.
<p> In your application, you must <ahref="ntqtranslator.html#load">TQTranslator::load</a>() the translation
<p> In your application, you must <ahref="tqtranslator.html#load">TQTranslator::load</a>() the translation
files appropriate for the user's language, and install them using <ahref="ntqapplication.html#installTranslator">TQApplication::installTranslator</a>().
<p> If you have been using the old TQt tools (<tt>tqtfindtr</tt>, <tt>msg2tqm</tt> and <tt>tqtmergetr</tt>), you can use <em>tqm2ts</em> to convert your old <tt>.qm</tt> files.
<p><em>linguist</em>, <em>lupdate</em> and <em>lrelease</em> are installed in the <tt>bin</tt>
@ -354,9 +354,9 @@ in <em>TQt Linguist</em> to access the user's manual; it contains a tutorial
to get you started.
<p> While these utilities offer a convenient way to create <tt>.qm</tt> files,
any system that writes <tt>.qm</tt> files is sufficient. You could make an
application that adds translations to a <ahref="ntqtranslator.html">TQTranslator</a> with
<ahref="ntqtranslator.html#insert">TQTranslator::insert</a>() and then writes a <tt>.qm</tt> file with
<ahref="ntqtranslator.html#save">TQTranslator::save</a>(). This way the translations can come from any
application that adds translations to a <ahref="tqtranslator.html">TQTranslator</a> with
<ahref="tqtranslator.html#insert">TQTranslator::insert</a>() and then writes a <tt>.qm</tt> file with
<ahref="tqtranslator.html#save">TQTranslator::save</a>(). This way the translations can come from any
source you choose.
<p><aname="qt-itself"></a>
TQt itself contains over 400 strings that will also need to be
<p>For a translation-aware application a translator object is created, a translation is loaded and the translator object installed into the application.</p>
<p>In production applications a more flexible approach, for example, loading translations according to locale, might be more appropriate. If the <tt>.ts</tt> files are all named according to a convention such as <em>appname_locale</em>, e.g. <tt>tt2_fr</tt>, <tt>tt2_de</tt> etc, then the code above will load the current locale's translation at runtime.</p>
<p>Three tutorials are presented. The first demonstrates the creation of a <ahref="ntqtranslator.html">TQTranslator</a> object. It also shows the simplest use of the <tt>tr()</tt> function to mark user-visible source text for translation. The second tutorial explains how to make the application load the translation file applicable to the current locale. It also shows the use of the two-argument form of <tt>tr()</tt> which provides additional information to the translator. The third tutorial explains how identical source texts can be distinguished even when they occur in the same context. This tutorial also discusses how the translation tools help minimize the translator's work when an application is upgraded.</p>
<p>Three tutorials are presented. The first demonstrates the creation of a <ahref="tqtranslator.html">TQTranslator</a> object. It also shows the simplest use of the <tt>tr()</tt> function to mark user-visible source text for translation. The second tutorial explains how to make the application load the translation file applicable to the current locale. It also shows the use of the two-argument form of <tt>tr()</tt> which provides additional information to the translator. The third tutorial explains how identical source texts can be distinguished even when they occur in the same context. This tutorial also discusses how the translation tools help minimize the translator's work when an application is upgraded.</p>
<h4><aname="2-1"></a>Tutorial 1: Loading and Using Translations</h4>
<p>This example is a reworking of the <ahref="tutorial1-01.html">"hello-world"</a> example from <ahref="tutorial.html">Tutorial #1</a>, with a Latin translation. The <em>Tutorial 1 Screenshot, English version</em>, above, shows the English version.</p>
<h5><aname="2-1-1"></a>Line by Line Walk-through</h5>
<!-- index TQTranslator --><p>This line includes the definition of the <ahref="ntqtranslator.html">TQTranslator</a> class. Objects of this class provide translations for user-visible text.</p>
<!-- index TQTranslator --><p>This line includes the definition of the <ahref="tqtranslator.html">TQTranslator</a> class. Objects of this class provide translations for user-visible text.</p>
<!-- index tt1_la.qm --><p>Tries to load a file called <tt>tt1_la.qm</tt> (the <tt>.qm</tt> file extension is implicit) that contains Latin translations for the source texts used in the program. No error will occur if the file is not found.</p>
<!-- index TQApplication!installTranslator() --><!-- index installTranslator()!TQApplication --><pre> app.<ahref="ntqapplication.html#installTranslator">installTranslator</a>( &translator );
@ -341,8 +341,8 @@ TRANSLATIONS = tt2_fr.ts \
</pre>
<p>Note the use of <tt>tr()</tt> to support different keys in other languages. "Ctrl+Q" is a good choice for Quit in English, but a Dutch translator might want to use "Ctrl+A" (for Afsluiten) and a German translator "Strg+E" (for Beenden). When using <tt>tr()</tt> for Ctrl key accelerators, the two argument form should be used with the second argument describing the function that the accelerator performs.</p>
<!-- index main() --><p>Our <tt>main()</tt> function is defined in <tt>main.cpp</tt> as usual.</p>
<!-- index TQTextCodec!locale() --><!-- index locale()!TQTextCodec --><!-- index LANG!Environment Variable --><!-- index Environment Variables!LANG --><p>We choose which translation to use according to the current locale. <ahref="tqtextcodec.html#locale">TQTextCodec::locale</a>() can be influenced by setting the <tt>LANG</tt> environment variable, for example. Notice that the use of a naming convention that incorporates the locale for <tt>.qm</tt> message files, (and <tt>.ts</tt> files), makes it easy to implement choosing the translation file according to locale.</p>
@ -463,8 +463,8 @@ TRANSLATIONS = tt3_pt.ts
<ahref="tqmainwindow.html#menuBar">menuBar</a>()->insertItem( <ahref="tqobject.html#tr">tr</a>("&Help"), help );
</pre>
<p>We also need to translate the menu items. Note that the two argument form of <tt>tr()</tt> is used for the keyboard accelerator, "Ctrl+Q", since the second argument is the only clue the translator has to indicate what function that accelerator will perform.</p>
<!-- index main() --><p>The <tt>main()</tt> function in <tt>main.cpp</tt> is the same as the one in <ahref="linguist-manual-4.html#2-2">Tutorial 2</a>. In particular it chooses a translation file based on the current locale.</p>
<aname="2-3"></a><p><ahref="qmotifwidget.html">TQMotifWidget</a> can be used together with <ahref="ntqdesktopwidget.html">TQDesktopWidget</a> to create
<aname="2-3"></a><p><ahref="qmotifwidget.html">TQMotifWidget</a> can be used together with <ahref="tqdesktopwidget.html">TQDesktopWidget</a> to create
top-level windows on multiple screens. A common mistake is to create
a TQMotifWidget on a non-default screen while the Xt/Motif widgets are
created on the default screen. The solution is to specify the screen
Adds the message file <em>mf</em> to the list of message files to be used
for translations.
@ -911,7 +911,7 @@ for translations.
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.
<p><p>See also <ahref="#removeTranslator">removeTranslator</a>(), <ahref="#translate">translate</a>(), and <ahref="ntqtranslator.html#load">TQTranslator::load</a>().
<p><p>See also <ahref="#removeTranslator">removeTranslator</a>(), <ahref="#translate">translate</a>(), and <ahref="tqtranslator.html#load">TQTranslator::load</a>().
Sends event <em>e</em> to <em>receiver</em>: <em>receiver</em>->event(<em>e</em>).
Returns the value that is returned from the receiver's event handler.
@ -1068,7 +1068,7 @@ Instead, based on meta information like <a href="tqobject.html#className">TQObje
able to customize any kind of widget.
<p><p>See also <ahref="tqstyle.html#polish">TQStyle::polish</a>(), <ahref="tqwidget.html#polish">TQWidget::polish</a>(), <ahref="#setPalette">setPalette</a>(), and <ahref="#setFont">setFont</a>().
</h3><p><b>Note:</b> This function is <ahref="threads.html#threadsafe">thread-safe</a> when TQt is built withthread support.</p>
Adds the event <em>event</em> with the object <em>receiver</em> as the receiver of the
@ -1086,7 +1086,7 @@ Processes pending events, for 3 seconds or until there are no more
events to process, whichever is shorter.
<p> You can call this function occasionally when your program is busy
performing a long operation (e.g. copying a file).
<p><p>See also <ahref="#exec">exec</a>(), <ahref="tqtimer.html">TQTimer</a>, and <ahref="ntqeventloop.html#processEvents">TQEventLoop::processEvents</a>().
<p><p>See also <ahref="#exec">exec</a>(), <ahref="tqtimer.html">TQTimer</a>, and <ahref="tqeventloop.html#processEvents">TQEventLoop::processEvents</a>().
<p>Examples: <ahref="fileiconview-example.html#x808">fileiconview/tqfileiconview.cpp</a> and <ahref="ftpclient-example.html#x778">network/ftpclient/main.cpp</a>.
@ -1096,7 +1096,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
there are no more events to process, whichever is shorter.
<p> You can call this function occasionally when you program is busy
doing a long operation (e.g. copying a file).
<p><p>See also <ahref="#exec">exec</a>(), <ahref="tqtimer.html">TQTimer</a>, and <ahref="ntqeventloop.html#processEvents">TQEventLoop::processEvents</a>().
<p><p>See also <ahref="#exec">exec</a>(), <ahref="tqtimer.html">TQTimer</a>, and <ahref="tqeventloop.html#processEvents">TQEventLoop::processEvents</a>().
Removes the message file <em>mf</em> from the list of message files used by
this application. (It does not delete the message file from the file
@ -1185,7 +1185,7 @@ See <a href="tqsessionmanager.html#allowsInteraction">TQSessionManager::allowsIn
<ahref="tqsessionmanager.html#allowsErrorInteraction">TQSessionManager::allowsErrorInteraction</a>() for details.
<p><p>See also <ahref="#isSessionRestored">isSessionRestored</a>(), <ahref="#sessionId">sessionId</a>(), <ahref="#commitData">commitData</a>(), and <ahref="session.html">the Session Management overview</a>.
<p> Sends event <em>event</em> directly to receiver <em>receiver</em>, using the
@ -1630,13 +1630,13 @@ the output text will be very long (as for help texts).
<p><em>comment</em> is a disambiguating comment, for when the same <em>sourceText</em> is used in different roles within the same context. By
default, it is null. <em>encoding</em> indicates the 8-bit encoding of
character stings
<p> See the <ahref="ntqtranslator.html">TQTranslator</a> documentation for more information about
<p> See the <ahref="tqtranslator.html">TQTranslator</a> documentation for more information about
contexts and comments.
<p> If none of the message files contain a translation for <em>sourceText</em> in <em>context</em>, this function returns a <ahref="tqstring.html">TQString</a>
equivalent of <em>sourceText</em>. The encoding of <em>sourceText</em> is
specified by <em>encoding</em>; it defaults to <ahref="#Encoding-enum">DefaultCodec</a>.
<p> This function is not virtual. You can use alternative translation
techniques by subclassing <ahref="ntqtranslator.html">TQTranslator</a>.
techniques by subclassing <ahref="tqtranslator.html">TQTranslator</a>.
<p><b>Warning:</b> This method is reentrant only if all translators are
installed <em>before</em> calling this method. Installing or removing
translators while performing translations is not supported. Doing
<p>This property holds whether the widget is under the mouse cursor.
<p>This value is not updated properly during drag and drop
operations.
<p> <p>See also <a href="ntqevent.html#Type-enum">QEvent::Enter</a> and <a href="ntqevent.html#Type-enum">QEvent::Leave</a>.
<p> <p>See also <a href="tqevent.html#Type-enum">TQEvent::Enter</a> and <a href="tqevent.html#Type-enum">TQEvent::Leave</a>.
<p>Get this property's value with <a href="tqwidget.html#hasMouse">hasMouse</a>().
<p><ahref="qchildevent-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@ -52,22 +52,22 @@ events.
<p>
<p> Child events are sent to objects when children are inserted or
removed.
<p> A <ahref="ntqevent.html#Type-enum">ChildRemoved</a> event is sent immediately, but a <ahref="ntqevent.html#Type-enum">ChildInserted</a> event is <em>posted</em> (with <ahref="ntqapplication.html#postEvent">TQApplication::postEvent</a>()).
<p> A <ahref="tqevent.html#Type-enum">ChildRemoved</a> event is sent immediately, but a <ahref="tqevent.html#Type-enum">ChildInserted</a> event is <em>posted</em> (with <ahref="ntqapplication.html#postEvent">TQApplication::postEvent</a>()).
<p> Note that if a child is removed immediately after it is inserted,
the <ahref="ntqevent.html#Type-enum">ChildInserted</a> event may be suppressed, but the <ahref="ntqevent.html#Type-enum">ChildRemoved</a> event will always be sent. In this case there will be
a <ahref="ntqevent.html#Type-enum">ChildRemoved</a> event without a corresponding <ahref="ntqevent.html#Type-enum">ChildInserted</a>
the <ahref="tqevent.html#Type-enum">ChildInserted</a> event may be suppressed, but the <ahref="tqevent.html#Type-enum">ChildRemoved</a> event will always be sent. In this case there will be
a <ahref="tqevent.html#Type-enum">ChildRemoved</a> event without a corresponding <ahref="tqevent.html#Type-enum">ChildInserted</a>
event.
<p> The handler for these events is <ahref="tqobject.html#childEvent">TQObject::childEvent</a>().
<p>See also <ahref="events.html">Event Classes</a>.
<p> The <em>type</em> parameter must be either <ahref="ntqevent.html#Type-enum">TQEvent::FocusIn</a> or <ahref="ntqevent.html#Type-enum">TQEvent::FocusOut</a>.
<p> The <em>type</em> parameter must be either <ahref="tqevent.html#Type-enum">TQEvent::FocusIn</a> or <ahref="tqevent.html#Type-enum">TQEvent::FocusOut</a>.
<p><ahref="qkeyevent-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@ -71,11 +71,11 @@ mouse and keyboard events for a widget.
<p><p>See also <ahref="qfocusevent.html">TQFocusEvent</a>, <ahref="tqwidget.html#grabKeyboard">TQWidget::grabKeyboard</a>(), and <ahref="events.html">Event Classes</a>.
<p> The <em>type</em> parameter must be <ahref="ntqevent.html#Type-enum">TQEvent::KeyPress</a> or <ahref="ntqevent.html#Type-enum">TQEvent::KeyRelease</a>. If <em>key</em> is 0 the event is not a result of a
<p> The <em>type</em> parameter must be <ahref="tqevent.html#Type-enum">TQEvent::KeyPress</a> or <ahref="tqevent.html#Type-enum">TQEvent::KeyRelease</a>. If <em>key</em> is 0 the event is not a result of a
known key (e.g. it may be the result of a compose sequence or
keyboard macro). <em>ascii</em> is the ASCII code of the key that was
pressed or released. <em>state</em> holds the keyboard modifiers. <em>text</em> is the Unicode text that the key generated. If <em>autorep</em> is
<p><ahref="qmouseevent-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@ -84,29 +84,29 @@ disable mouse and keyboard events for a widget.
<p><p>See also <ahref="tqwidget.html#mouseTracking-prop">TQWidget::mouseTracking</a>, <ahref="tqwidget.html#grabMouse">TQWidget::grabMouse</a>(), <ahref="ntqcursor.html#pos">TQCursor::pos</a>(), and <ahref="events.html">Event Classes</a>.
<p> The <em>pos</em> parameter specifies the position relative to the
receiving widget. <em>button</em> specifies the <ahref="ntqt.html#ButtonState-enum">button</a> that caused the event, which should be <ahref="ntqt.html#ButtonState-enum">TQt::NoButton</a> (0), if <em>type</em> is <ahref="ntqevent.html#Type-enum">MouseMove</a>. <em>state</em> is the
receiving widget. <em>button</em> specifies the <ahref="ntqt.html#ButtonState-enum">button</a> that caused the event, which should be <ahref="ntqt.html#ButtonState-enum">TQt::NoButton</a> (0), if <em>type</em> is <ahref="tqevent.html#Type-enum">MouseMove</a>. <em>state</em> is the
<ahref="ntqt.html#ButtonState-enum">ButtonState</a> at the time of the
event.
<p> The <ahref="#globalPos">globalPos</a>() is initialized to <ahref="ntqcursor.html#pos">TQCursor::pos</a>(), which may not be
appropriate. Use the other constructor to specify the global
<p> The <em>type</em> parameter must be <ahref="ntqevent.html#Type-enum">TQEvent::MouseButtonPress</a>, <ahref="ntqevent.html#Type-enum">TQEvent::MouseButtonRelease</a>, <ahref="ntqevent.html#Type-enum">TQEvent::MouseButtonDblClick</a> or <ahref="ntqevent.html#Type-enum">TQEvent::MouseMove</a>.
<p> The <em>type</em> parameter must be <ahref="tqevent.html#Type-enum">TQEvent::MouseButtonPress</a>, <ahref="tqevent.html#Type-enum">TQEvent::MouseButtonRelease</a>, <ahref="tqevent.html#Type-enum">TQEvent::MouseButtonDblClick</a> or <ahref="tqevent.html#Type-enum">TQEvent::MouseMove</a>.
<p> The <em>pos</em> parameter specifies the position relative to the
receiving widget. <em>globalPos</em> is the position in absolute
coordinates. <em>button</em> specifies the <ahref="ntqt.html#ButtonState-enum">button</a> that caused the event, which should be <ahref="ntqt.html#ButtonState-enum">TQt::NoButton</a> (0), if <em>type</em> is <ahref="ntqevent.html#Type-enum">MouseMove</a>. <em>state</em> is the
coordinates. <em>button</em> specifies the <ahref="ntqt.html#ButtonState-enum">button</a> that caused the event, which should be <ahref="ntqt.html#ButtonState-enum">TQt::NoButton</a> (0), if <em>type</em> is <ahref="tqevent.html#Type-enum">MouseMove</a>. <em>state</em> is the
<ahref="ntqt.html#ButtonState-enum">ButtonState</a> at the time of the
event.
<p>
@ -187,11 +187,11 @@ global position returned by <a href="#globalPos">globalPos</a>() to avoid a shak
<p> Returns the button state (a combination of mouse buttons and
keyboard modifiers), i.e. what buttons and keys were being pressed
immediately before the event was generated.
<p> This means that if you have a <ahref="ntqevent.html#Type-enum">TQEvent::MouseButtonPress</a> or a <ahref="ntqevent.html#Type-enum">TQEvent::MouseButtonDblClick</a><ahref="#state">state</a>() will <em>not</em> include the mouse
<p> This means that if you have a <ahref="tqevent.html#Type-enum">TQEvent::MouseButtonPress</a> or a <ahref="tqevent.html#Type-enum">TQEvent::MouseButtonDblClick</a><ahref="#state">state</a>() will <em>not</em> include the mouse
button that's pressed. But once the mouse button has been
released, the <ahref="ntqevent.html#Type-enum">TQEvent::MouseButtonRelease</a> event will have the
released, the <ahref="tqevent.html#Type-enum">TQEvent::MouseButtonRelease</a> event will have the
<ahref="#button">button</a>() that was pressed.
<p> This value is mainly interesting for <ahref="ntqevent.html#Type-enum">TQEvent::MouseMove</a>; for the
<p> This value is mainly interesting for <ahref="tqevent.html#Type-enum">TQEvent::MouseMove</a>; for the
other cases, button() is more useful.
<p> The returned value is <ahref="ntqt.html#ButtonState-enum">LeftButton</a>, <ahref="ntqt.html#ButtonState-enum">RightButton</a>, <ahref="ntqt.html#ButtonState-enum">MidButton</a>,
<ahref="ntqt.html#ButtonState-enum">ShiftButton</a>, <ahref="ntqt.html#ButtonState-enum">ControlButton</a> and <ahref="ntqt.html#ButtonState-enum">AltButton</a> OR'ed together.
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQDesktopWidget</h1>
<p>This is the complete list of member functions for
<ahref="ntqdesktopwidget.html">TQDesktopWidget</a>, including inherited members.
<ahref="tqdesktopwidget.html">TQDesktopWidget</a>, including inherited members.
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQEvent</h1>
<p>This is the complete list of member functions for
<ahref="ntqevent.html">TQEvent</a>, including inherited members.
<ahref="tqevent.html">TQEvent</a>, including inherited members.
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQEventLoop</h1>
<p>This is the complete list of member functions for
<ahref="ntqeventloop.html">TQEventLoop</a>, including inherited members.
<ahref="tqeventloop.html">TQEventLoop</a>, including inherited members.
This virtual function receives events to an object and should
return TRUE if the event <em>e</em> was recognized and processed.
@ -488,7 +488,7 @@ behavior of an object.
<p><p>See also <ahref="#installEventFilter">installEventFilter</a>(), <ahref="#timerEvent">timerEvent</a>(), <ahref="ntqapplication.html#sendEvent">TQApplication::sendEvent</a>(), <ahref="ntqapplication.html#postEvent">TQApplication::postEvent</a>(), and <ahref="tqwidget.html#event">TQWidget::event</a>().
<p>Reimplemented in <ahref="tqwidget.html#event">TQWidget</a>.
Filters events if this object has been installed as an event
filter for the <em>watched</em> object.
@ -867,7 +867,7 @@ some provide more. If TQt is unable to deliver the requested
number of timer clicks, it will silently discard some.
<p> The TQTimer class provides a high-level programming interface with
one-shot timers and timer signals instead of events.
<p><p>See also <ahref="#timerEvent">timerEvent</a>(), <ahref="#killTimer">killTimer</a>(), <ahref="#killTimers">killTimers</a>(), <ahref="ntqeventloop.html#awake">TQEventLoop::awake</a>(), and <ahref="ntqeventloop.html#aboutToBlock">TQEventLoop::aboutToBlock</a>().
<p><p>See also <ahref="#timerEvent">timerEvent</a>(), <ahref="#killTimer">killTimer</a>(), <ahref="#killTimers">killTimers</a>(), <ahref="tqeventloop.html#awake">TQEventLoop::awake</a>(), and <ahref="tqeventloop.html#aboutToBlock">TQEventLoop::aboutToBlock</a>().
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQTranslator</h1>
<p>This is the complete list of member functions for
<ahref="ntqtranslator.html">TQTranslator</a>, including inherited members.
<ahref="tqtranslator.html">TQTranslator</a>, including inherited members.
<p> An object of this class contains a set of <ahref="qtranslatormessage.html">TQTranslatorMessage</a>
<p> An object of this class contains a set of <ahref="tqtranslatormessage.html">TQTranslatorMessage</a>
objects, each of which specifies a translation from a source
language to a target language. TQTranslator provides functions to
look up translations, add new ones, remove them, load and save
@ -148,7 +148,7 @@ translations.
<p> Note that when TQTranslator loads a stripped file, most functions
do not work. The functions that do work with stripped files are
explicitly documented as such.
<p><p>See also <ahref="qtranslatormessage.html">TQTranslatorMessage</a>, <ahref="ntqapplication.html#installTranslator">TQApplication::installTranslator</a>(), <ahref="ntqapplication.html#removeTranslator">TQApplication::removeTranslator</a>(), <ahref="tqobject.html#tr">TQObject::tr</a>(), <ahref="ntqapplication.html#translate">TQApplication::translate</a>(), <ahref="environment.html">Environment Classes</a>, and <ahref="i18n.html">Internationalization with TQt</a>.
<p><p>See also <ahref="tqtranslatormessage.html">TQTranslatorMessage</a>, <ahref="ntqapplication.html#installTranslator">TQApplication::installTranslator</a>(), <ahref="ntqapplication.html#removeTranslator">TQApplication::removeTranslator</a>(), <ahref="tqobject.html#tr">TQObject::tr</a>(), <ahref="ntqapplication.html#translate">TQApplication::translate</a>(), <ahref="environment.html">Environment Classes</a>, and <ahref="i18n.html">Internationalization with TQt</a>.
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQTranslatorMessage</h1>
<p>This is the complete list of member functions for
<ahref="qtranslatormessage.html">TQTranslatorMessage</a>, including inherited members.
<ahref="tqtranslatormessage.html">TQTranslatorMessage</a>, including inherited members.
for translation tools such as <ahref="linguist-manual.html">TQt
Linguist</a>. It is provided simply to make the API complete
and regular.
<p> For a <ahref="ntqtranslator.html">TQTranslator</a> object, a lookup key is a triple (<em>context</em>, <em>source text</em>, <em>comment</em>) that uniquely identifies a message. An
<p> For a <ahref="tqtranslator.html">TQTranslator</a> object, a lookup key is a triple (<em>context</em>, <em>source text</em>, <em>comment</em>) that uniquely identifies a message. An
extended key is a quadruple (<em>hash</em>, <em>context</em>, <em>source text</em>, <em>comment</em>), where <em>hash</em> is computed from the source text
and the comment. Unless you plan to read and write messages
yourself, you need not worry about the hash value.
<p> TQTranslatorMessage stores this triple or quadruple and the relevant
translation if there is any.
<p><p>See also <ahref="ntqtranslator.html">TQTranslator</a>, <ahref="environment.html">Environment Classes</a>, and <ahref="i18n.html">Internationalization with TQt</a>.
<p><p>See also <ahref="tqtranslator.html">TQTranslator</a>, <ahref="environment.html">Environment Classes</a>, and <ahref="i18n.html">Internationalization with TQt</a>.
<p><ahref="tqwidget-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@ -663,7 +663,7 @@ parent.
<ahref="#close">close</a>() is called).
<p></ul>
<p> There are also some rather obscure events. They are listed in
<ahref="qevent-h.html">ntqevent.h</a> and you need to reimplement <ahref="#event">event</a>() to handle them.
<ahref="tqevent-h.html">tqevent.h</a> and you need to reimplement <ahref="#event">event</a>() to handle them.
The default implementation of event() handles Tab and Shift+Tab
(to move the keyboard focus), and passes on most other events to
one of the more specialized handlers above.
@ -681,7 +681,7 @@ indicates a "good" size for the widget.
<p><li> If your widget is a top-level window, <ahref="#setCaption">setCaption</a>() and <ahref="#setIcon">setIcon</a>() set
the title bar and icon respectively.
<p></ul>
<p><p>See also <ahref="ntqevent.html">TQEvent</a>, <ahref="tqpainter.html">TQPainter</a>, <ahref="qgridlayout.html">TQGridLayout</a>, <ahref="qboxlayout.html">TQBoxLayout</a>, and <ahref="abstractwidgets.html">Abstract Widget Classes</a>.
<p><p>See also <ahref="tqevent.html">TQEvent</a>, <ahref="tqpainter.html">TQPainter</a>, <ahref="qgridlayout.html">TQGridLayout</a>, <ahref="qboxlayout.html">TQBoxLayout</a>, and <ahref="abstractwidgets.html">Abstract Widget Classes</a>.
@ -977,7 +977,7 @@ update the widget using <a href="#update">update</a>().
widget.
<p><p>See also <ahref="#enabled-prop">enabled</a>, <ahref="#enabled-prop">enabled</a>, <ahref="#repaint">repaint</a>(), <ahref="#update">update</a>(), and <ahref="#clipRegion">clipRegion</a>().
This is the main event handler; it handles event <em>e</em>. You can
reimplement this function in a subclass, but we recommend using
@ -1424,7 +1424,7 @@ widget's children.
<p><p>See also <ahref="#sizePolicy-prop">sizePolicy</a>.
<p>Examples: <ahref="tutorial2-09.html#x2647">chart/optionsform.cpp</a> and <ahref="simple-font-demo-example.html#x2858">fonts/simple-tqfont-demo/viewer.cpp</a>.
Returns the desktop widget (also called the root window).
.PP
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.
.PP
.nf
.br
QDesktopWidget *d = QApplication::desktop();
TQDesktopWidget *d = QApplication::desktop();
.br
int w = d->width(); // returns desktop width
.br
@ -860,12 +860,12 @@ See also setDoubleClickInterval().
This function enters the main event loop (recursively). Do not call it unless you really know what you are doing.
.PP
Use QApplication::eventLoop()->enterLoop() instead.
Returns the application event loop. This function will return zero if called during and after destroying QApplication.
.PP
To create your own instance of QEventLoop or QEventLoop subclass create it before you create the QApplication object.
To create your own instance of TQEventLoop or TQEventLoop subclass create it before you create the QApplication object.
.PP
See also QEventLoop.
See also TQEventLoop.
.PP
Example: distributor/distributor.ui.h.
.SH "int QApplication::exec ()"
@ -945,12 +945,12 @@ See also setGlobalMouseTracking().
This function returns TRUE if there are pending events; otherwise returns FALSE. Pending events can be either from the window system or posted events using QApplication::postEvent().
.SH "int QApplication::horizontalAlignment ( int align )\fC [static]\fR"
Strips out vertical alignment flags and transforms an alignment \fIalign\fR of AlignAuto into AlignLeft or AlignRight according to the language used. The other horizontal alignment flags are left untouched.
Adds the message file \fImf\fR to the list of message files to be used for translations.
.PP
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.
.PP
See also removeTranslator(), translate(), and QTranslator::load().
See also removeTranslator(), translate(), and TQTranslator::load().
Sends event \fIe\fR to \fIreceiver\fR: \fIreceiver\fR->event(\fIe\fR). Returns the value that is returned from the receiver's event handler.
.PP
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).
@ -1071,7 +1071,7 @@ Usually widgets call this automatically when they are polished. It may be used t
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.
.PP
See also TQStyle::polish(), TQWidget::polish(), setPalette(), and setFont().
\fBNote:\fR This function is thread-safe when TQt is built withthread support.</p> Adds the event \fIevent\fR with the object \fIreceiver\fR as the receiver of the event, to an event queue and returns immediately.
.PP
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.
@ -1084,7 +1084,7 @@ Processes pending events, for 3 seconds or until there are no more events to pro
.PP
You can call this function occasionally when your program is busy performing a long operation (e.g. copying a file).
.PP
See also exec(), TQTimer, and QEventLoop::processEvents().
See also exec(), TQTimer, and TQEventLoop::processEvents().
.PP
Examples:
.)l fileiconview/tqfileiconview.cpp and network/ftpclient/main.cpp.
@ -1095,7 +1095,7 @@ Processes pending events for \fImaxtime\fR milliseconds or until there are no mo
.PP
You can call this function occasionally when you program is busy doing a long operation (e.g. copying a file).
.PP
See also exec(), TQTimer, and QEventLoop::processEvents().
See also exec(), TQTimer, and TQEventLoop::processEvents().
.SH "void QApplication::processOneEvent ()"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
@ -1133,7 +1133,7 @@ See also addLibraryPath(), libraryPaths(), and setLibraryPaths().
\fBNote:\fR This function is thread-safe when TQt is built withthread support.</p> Removes all events posted using postEvent() for \fIreceiver\fR.
.PP
The events are \fInot\fR 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 \fIreceiver\fR to break one or more invariants.
Removes the message file \fImf\fR from the list of message files used by this application. (It does not delete the message file from the file system.)
.PP
See also installTranslator(), translate(), and TQObject::tr().
@ -1162,14 +1162,14 @@ Note that you should never exit the application within this function. Instead, t
\fBWarning:\fR Within this function, no user interaction is possible, \fIunless\fR you ask the session manager \fIsm\fR for explicit permission. See TQSessionManager::allowsInteraction() and TQSessionManager::allowsErrorInteraction() for details.
.PP
See also isSessionRestored(), sessionId(), commitData(), and the Session Management overview.
@ -1551,11 +1551,11 @@ TQObject::tr() and TQObject::trUtf8() provide this functionality more convenient
.PP
\fIcomment\fR is a disambiguating comment, for when the same \fIsourceText\fR is used in different roles within the same context. By default, it is null. \fIencoding\fR indicates the 8-bit encoding of character stings
.PP
See the QTranslator documentation for more information about contexts and comments.
See the TQTranslator documentation for more information about contexts and comments.
.PP
If none of the message files contain a translation for \fIsourceText\fR in \fIcontext\fR, this function returns a TQString equivalent of \fIsourceText\fR. The encoding of \fIsourceText\fR is specified by \fIencoding\fR; it defaults to DefaultCodec.
.PP
This function is not virtual. You can use alternative translation techniques by subclassing QTranslator.
This function is not virtual. You can use alternative translation techniques by subclassing TQTranslator.
.PP
\fBWarning:\fR This method is reentrant only if all translators are installed \fIbefore\fR 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.
@ -33,7 +33,7 @@ The QCustomEvent class provides support for custom events.
.PP
QCustomEvent is a generic event class for user-defined events. User defined events can be sent to widgets or other TQObject instances using QApplication::postEvent() or QApplication::sendEvent(). Subclasses of TQObject can easily receive custom events by implementing the TQObject::customEvent() event handler function.
.PP
QCustomEvent objects should be created with a type ID that uniquely identifies the event type. To avoid clashes with the Qt-defined events types, the value should be at least as large as the value of the "User" entry in the QEvent::Type enum.
QCustomEvent objects should be created with a type ID that uniquely identifies the event type. To avoid clashes with the Qt-defined events types, the value should be at least as large as the value of the "User" entry in the TQEvent::Type enum.
.PP
QCustomEvent contains a generic void* data member that may be used for transferring event-specific data to the receiver. Note that since events are normally delivered asynchronously, the data pointer, if used, must remain valid until the event has been received and processed.
.PP
@ -92,9 +92,9 @@ Example:
See also TQWidget::customEvent(), QApplication::notify(), and Event Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QCustomEvent::QCustomEvent ( int type )"
Constructs a custom event object with event type \fItype\fR. The value of \fItype\fR must be at least as large as QEvent::User. The data pointer is set to 0.
Constructs a custom event object with event type \fItype\fR. The value of \fItype\fR must be at least as large as TQEvent::User. The data pointer is set to 0.
.SH "QCustomEvent::QCustomEvent ( Type type, void * data )"
Constructs a custom event object with the event type \fItype\fR and a pointer to \fIdata\fR. (Note that any int value may safely be cast to QEvent::Type).
Constructs a custom event object with the event type \fItype\fR and a pointer to \fIdata\fR. (Note that any int value may safely be cast to TQEvent::Type).
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,19 +7,19 @@
.ad l
.nh
.SH NAME
QDesktopWidget \- Access to screen information on multi-head systems
TQDesktopWidget \- Access to screen information on multi-head systems
.SH SYNOPSIS
\fC#include <ntqdesktopwidget.h>\fR
\fC#include <tqdesktopwidget.h>\fR
.PP
Inherits TQWidget.
.PP
.SS "Public Members"
.in +1c
.ti -1c
.BI "\fBQDesktopWidget\fR ()"
.BI "\fBTQDesktopWidget\fR ()"
.br
.ti -1c
.BI "\fB~QDesktopWidget\fR ()"
.BI "\fB~TQDesktopWidget\fR ()"
.br
.ti -1c
.BI "bool \fBisVirtualDesktop\fR () const"
@ -65,11 +65,11 @@ Inherits TQWidget.
.br
.in -1c
.SH DESCRIPTION
The QDesktopWidget class provides access to screen information on multi-head systems.
The TQDesktopWidget class provides access to screen information on multi-head systems.
.PP
Systems with more than one graphics card and monitor can manage the physical screen space available either as multiple desktops, or as a large virtual desktop, which usually has the size of the bounding rectangle of all the screens (see isVirtualDesktop()). For an application, one of the available screens is the primary screen, i.e. the screen where the main widget resides (see primaryScreen()). All windows opened in the context of the application must be constrained to the boundaries of the primary screen; for example, it would be inconvenient if a dialog box popped up on a different screen, or split over two screens.
.PP
The QDesktopWidget provides information about the geometry of the available screens with screenGeometry(). The number of screens available is returned by numScreens(). The screen number that a particular point or widget is located in is returned by screenNumber().
The TQDesktopWidget provides information about the geometry of the available screens with screenGeometry(). The number of screens available is returned by numScreens(). The screen number that a particular point or widget is located in is returned by screenNumber().
.PP
Widgets provided by TQt use this class, for example, to place tooltips, menus and dialog boxes according to the parent or application widget.
.PP
@ -85,45 +85,45 @@ In the illustration above, Application One's primary screen is screen 0, and App
.PP
See also Advanced Widgets and Environment Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QDesktopWidget::QDesktopWidget ()"
.SH "TQDesktopWidget::TQDesktopWidget ()"
Creates the desktop widget.
.PP
If the system supports a virtual desktop, this widget will have the size of the virtual desktop; otherwise this widget will have the size of the primary screen.
.PP
Instead of using QDesktopWidget directly, use QApplication::desktop().
.SH "QDesktopWidget::~QDesktopWidget ()"
Instead of using TQDesktopWidget directly, use QApplication::desktop().
Returns the available geometry of the screen with index \fIscreen\fR. What is available will be subrect of screenGeometry() based on what the platform decides is available (for example excludes the Dock and Menubar on Mac OS X, or the taskbar on Windows).
Returns TRUE if the system manages the available screens in a virtual desktop; otherwise returns FALSE.
.PP
For virtual desktops, screen() will always return the same widget. The size of the virtual desktop is the size of this desktop widget.
.SH "int QDesktopWidget::numScreens () const"
.SH "int TQDesktopWidget::numScreens () const"
Returns the number of available screens.
.PP
See also primaryScreen().
.SH "int QDesktopWidget::primaryScreen () const"
.SH "int TQDesktopWidget::primaryScreen () const"
Returns the index of the primary screen.
.PP
See also numScreens().
.SH "void QDesktopWidget::resized ( int screen )\fC [signal]\fR"
.SH "void TQDesktopWidget::resized ( int screen )\fC [signal]\fR"
This signal is emitted when the size of \fIscreen\fR changes.
.SH "TQWidget * QDesktopWidget::screen ( int screen = -1 )"
.SH "TQWidget * TQDesktopWidget::screen ( int screen = -1 )"
Returns a widget that represents the screen with index \fIscreen\fR. This widget can be used to draw directly on the desktop, using an unclipped painter like this:
.PP
.nf
@ -141,23 +141,23 @@ Returns a widget that represents the screen with index \fIscreen\fR. This widget
If the system uses a virtual desktop, the returned widget will have the geometry of the entire virtual desktop i.e. bounding every \fIscreen\fR.
.PP
See also primaryScreen(), numScreens(), and isVirtualDesktop().
The QEvent class is the base class of all event classes. Event objects contain event parameters.
The TQEvent class is the base class of all event classes. Event objects contain event parameters.
.PP
Qt's main event loop (QApplication::exec()) fetches native window system events from the event queue, translates them into QEvents and sends the translated events to TQObjects.
Qt's main event loop (QApplication::exec()) fetches native window system events from the event queue, translates them into TQEvents and sends the translated events to TQObjects.
.PP
In general, events come from the underlying window system (spontaneous() returns TRUE) but it is also possible to manually send events using QApplication::sendEvent() and QApplication::postEvent() (spontaneous() returns FALSE).
.PP
TQObjects receive events by having their TQObject::event() function called. The function can be reimplemented in subclasses to customize event handling and add additional event types; TQWidget::event() is a notable example. By default, events are dispatched to event handlers like TQObject::timerEvent() and TQWidget::mouseMoveEvent(). TQObject::installEventFilter() allows an object to intercept events destined for another object.
.PP
The basic QEvent contains only an event type parameter. Subclasses of QEvent contain additional parameters that describe the particular event.
The basic TQEvent contains only an event type parameter. Subclasses of TQEvent contain additional parameters that describe the particular event.
.PP
See also TQObject::event(), TQObject::installEventFilter(), TQWidget::event(), QApplication::sendEvent(), QApplication::postEvent(), QApplication::processEvents(), Environment Classes, and Event Classes.
.SS "Member Type Documentation"
.SH "QEvent::Type"
.SH "TQEvent::Type"
This enum type defines the valid event types in Qt. The event types and the specialized classes for each type are these:
.TP
\fCQEvent::None\fR - Not an event.
\fCTQEvent::None\fR - Not an event.
.TP
\fCQEvent::Accessibility\fR - Accessibility information is requested
\fCTQEvent::Accessibility\fR - Accessibility information is requested
It receives events from the window system and other sources. It then sends them to QApplication for processing and delivery.
.PP
QEventLoop allows the application programmer to have more control over event delivery. Programs that perform long operations can call either processOneEvent() or processEvents() with various ProcessEvent values OR'ed together to control which events should be delivered.
TQEventLoop allows the application programmer to have more control over event delivery. Programs that perform long operations can call either processOneEvent() or processEvents() with various ProcessEvent values OR'ed together to control which events should be delivered.
.PP
QEventLoop also allows the integration of an external event loop with the TQt event loop. The Motif Extension included with TQt includes a reimplementation of QEventLoop for merging TQt and Motif events together.
TQEventLoop also allows the integration of an external event loop with the TQt event loop. The Motif Extension included with TQt includes a reimplementation of TQEventLoop for merging TQt and Motif events together.
.PP
To use your own instance of QEventLoop or QEventLoop subclass create it before you create the QApplication object.
To use your own instance of TQEventLoop or TQEventLoop subclass create it before you create the QApplication object.
.PP
See also Main Window and Related Classes and Event Classes.
.SS "Member Type Documentation"
.SH "QEventLoop::ProcessEvents"
.SH "TQEventLoop::ProcessEvents"
This enum controls the types of events processed by the processEvents() functions.
.TP
\fCQEventLoop::AllEvents\fR - All events are processed
\fCTQEventLoop::AllEvents\fR - All events are processed
.TP
\fCQEventLoop::ExcludeUserInput\fR - Do not process user input events. ( ButtonPress, KeyPress, etc. )
\fCTQEventLoop::ExcludeUserInput\fR - Do not process user input events. ( ButtonPress, KeyPress, etc. )
.TP
\fCQEventLoop::ExcludeSocketNotifiers\fR - Do not process socket notifier events.
\fCTQEventLoop::ExcludeSocketNotifiers\fR - Do not process socket notifier events.
.TP
\fCQEventLoop::WaitForMore\fR - Wait for events if no pending events are available.
\fCTQEventLoop::WaitForMore\fR - Wait for events if no pending events are available.
.PP
See also processEvents().
.SH "QEventLoop::ProcessEventsFlags"
.SH "TQEventLoop::ProcessEventsFlags"
A \fCtypedef\fR to allow various ProcessEvents values to be OR'ed together.
Creates a QEventLoop object, this object becomes the global event loop object. There can only be one event loop object. The QEventLoop is usually constructed by calling QApplication::eventLoop(). To create your own event loop object create it before you instantiate the QApplication object.
Creates a TQEventLoop object, this object becomes the global event loop object. There can only be one event loop object. The TQEventLoop is usually constructed by calling QApplication::eventLoop(). To create your own event loop object create it before you instantiate the QApplication object.
.PP
The \fIparent\fR and \fIname\fR arguments are passed on to the TQObject constructor.
This signal is emitted before the event loop calls a function that could block.
.PP
See also awake().
.SH "int QEventLoop::activateSocketNotifiers ()"
.SH "int TQEventLoop::activateSocketNotifiers ()"
Activates all pending socket notifiers and returns the number of socket notifiers that were activated.
.SH "int QEventLoop::activateTimers ()"
.SH "int TQEventLoop::activateTimers ()"
Activates all TQt timers and returns the number of timers that were activated.
.PP
QEventLoop subclasses that do their own timer handling need to call this after the time returned by timeToWait() has elapsed.
TQEventLoop subclasses that do their own timer handling need to call this after the time returned by timeToWait() has elapsed.
.PP
Note: This function is only useful on systems where \fCselect()\fR is used to block the eventloop. On Windows, this function always returns 0. On MacOS X, this function always returns 0 when the GUI is enabled. On MacOS X, this function returns the documented value when the GUI is disabled.
.SH "void QEventLoop::awake ()\fC [signal]\fR"
.SH "void TQEventLoop::awake ()\fC [signal]\fR"
This signal is emitted after the event loop returns from a function that could block.
This function enters the main event loop (recursively). Do not call it unless you really know what you are doing.
.SH "int QEventLoop::exec ()\fC [virtual]\fR"
.SH "int TQEventLoop::exec ()\fC [virtual]\fR"
Enters the main event loop and waits until exit() is called, and returns the value that was set to exit().
.PP
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.
@ -148,7 +148,7 @@ Generally speaking, no user interaction can take place before calling exec(). As
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().
.PP
See also QApplication::quit(), exit(), and processEvents().
.SH "void QEventLoop::exit ( int retcode = 0 )\fC [virtual]\fR"
.SH "void TQEventLoop::exit ( int retcode = 0 )\fC [virtual]\fR"
Tells the event loop to exit with a return code.
.PP
After this function has been called, the event loop returns from the call to exec(). The exec() function returns \fIretcode\fR.
@ -158,13 +158,13 @@ By convention, a \fIretcode\fR of 0 means success, and any non-zero value indica
Note that unlike the C library function of the same name, this function \fIdoes\fR return to the caller -- it is event processing that stops.
.SH "void QEventLoop::processEvents ( ProcessEventsFlags flags, int maxTime )"
.SH "void TQEventLoop::processEvents ( ProcessEventsFlags flags, int maxTime )"
Process pending events that match \fIflags\fR for a maximum of \fImaxTime\fR milliseconds, or until there are no more events to process, which ever is shorter.
.PP
This function is especially useful if you have a long running operation and want to show its progress without allowing user input, i.e. by using the ExcludeUserInput flag.
@ -172,7 +172,7 @@ This function is especially useful if you have a long running operation and want
NOTE: This function will not process events continuously; it returns after all available events are processed.
.PP
NOTE: Specifying the WaitForMore flag makes no sense and will be ignored.
Registers \fInotifier\fR with the event loop. Subclasses need to reimplement this method to tie a socket notifier into another event loop. Reimplementations \fIMUST\fR call the base implementation.
Marks \fInotifier\fR as pending. The socket notifier will be activated the next time activateSocketNotifiers() is called.
.SH "int QEventLoop::timeToWait () const"
.SH "int TQEventLoop::timeToWait () const"
Returns the number of milliseconds that TQt needs to handle its timers or -1 if there are no timers running.
.PP
QEventLoop subclasses that do their own timer handling need to use this to make sure that Qt's timers continue to work.
TQEventLoop subclasses that do their own timer handling need to use this to make sure that Qt's timers continue to work.
.PP
Note: This function is only useful on systems where \fCselect()\fR is used to block the eventloop. On Windows, this function always returns -1. On MacOS X, this function always returns -1 when the GUI is enabled. On MacOS X, this function returns the documented value when the GUI is disabled.
Unregisters \fInotifier\fR from the event loop. Subclasses need to reimplement this method to tie a socket notifier into another event loop. Reimplementations \fIMUST\fR call the base implementation.
.SH "void QEventLoop::wakeUp ()\fC [virtual]\fR"
.SH "void TQEventLoop::wakeUp ()\fC [virtual]\fR"
\fBNote:\fR This function is thread-safe when TQt is built withthread support.</p>
.PP
Wakes up the event loop.
@ -215,7 +215,7 @@ Wakes up the event loop.
See also awake().
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqeventloop.html
.BR http://doc.trolltech.com/tqeventloop.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
@ -73,7 +73,7 @@ If the user clicks another widget, taking the focus out of the widget where the
See also Event Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QIMEvent::QIMEvent ( Type type, const TQString & text, int cursorPosition )"
Constructs a new QIMEvent with the accept flag set to FALSE. \fItype\fR can be one of QEvent::IMStartEvent, QEvent::IMComposeEvent or QEvent::IMEndEvent. \fItext\fR contains the current compostion string and \fIcursorPosition\fR the current position of the cursor inside \fItext\fR.
Constructs a new QIMEvent with the accept flag set to FALSE. \fItype\fR can be one of TQEvent::IMStartEvent, TQEvent::IMComposeEvent or TQEvent::IMEndEvent. \fItext\fR contains the current compostion string and \fIcursorPosition\fR the current position of the cursor inside \fItext\fR.
.SH "void QIMEvent::accept ()"
Sets the accept flag of the input method event object.
@ -65,7 +65,7 @@ See also QFocusEvent, TQWidget::grabKeyboard(), and Event Classes.
.SH "QKeyEvent::QKeyEvent ( Type type, int key, int ascii, int state, const TQString & text = TQString::null, bool autorep = FALSE, ushort count = 1 )"
Constructs a key event object.
.PP
The \fItype\fR parameter must be QEvent::KeyPress or QEvent::KeyRelease. If \fIkey\fR is 0 the event is not a result of a known key (e.g. it may be the result of a compose sequence or keyboard macro). \fIascii\fR is the ASCII code of the key that was pressed or released. \fIstate\fR holds the keyboard modifiers. \fItext\fR is the Unicode text that the key generated. If \fIautorep\fR is TRUE, isAutoRepeat() will be TRUE. \fIcount\fR is the number of single keys.
The \fItype\fR parameter must be TQEvent::KeyPress or TQEvent::KeyRelease. If \fIkey\fR is 0 the event is not a result of a known key (e.g. it may be the result of a compose sequence or keyboard macro). \fIascii\fR is the ASCII code of the key that was pressed or released. \fIstate\fR holds the keyboard modifiers. \fItext\fR is the Unicode text that the key generated. If \fIautorep\fR is TRUE, isAutoRepeat() will be TRUE. \fIcount\fR is the number of single keys.
.BI "virtual bool \fBeventFilter\fR ( TQObject * o, QEvent * e )"
.BI "virtual bool \fBeventFilter\fR ( TQObject * o, TQEvent * e )"
.br
.ti -1c
.BI "virtual void \fBsetShowSortIndicator\fR ( bool show )"
@ -670,7 +670,7 @@ This signal is emitted, when a drop event occurred on the viewport (not onto an
Ensures that item \fIi\fR is visible, scrolling the list view vertically if necessary and opening (expanding) any parent items if this is required to show the item.
.PP
See also itemRect() and QScrollView::ensureVisible().
.SH "bool QListView::eventFilter ( TQObject * o, QEvent * e )\fC [virtual]\fR"
.SH "bool QListView::eventFilter ( TQObject * o, TQEvent * e )\fC [virtual]\fR"
Redirects the event \fIe\fR relating to object \fIo\fR, for the viewport to mousePressEvent(), keyPressEvent() and friends.
QMouseEvent \- Parameters that describe a mouse event
.SH SYNOPSIS
\fC#include <ntqevent.h>\fR
\fC#include <tqevent.h>\fR
.PP
Inherits QEvent.
Inherits TQEvent.
.PP
.SS "Public Members"
.in +1c
@ -80,7 +80,7 @@ See also TQWidget::mouseTracking, TQWidget::grabMouse(), QCursor::pos(), and Eve
.SH "QMouseEvent::QMouseEvent ( Type type, const TQPoint & pos, int button, int state )"
Constructs a mouse event object.
.PP
The \fItype\fR parameter must be one of QEvent::MouseButtonPress, QEvent::MouseButtonRelease, QEvent::MouseButtonDblClick or QEvent::MouseMove.
The \fItype\fR parameter must be one of TQEvent::MouseButtonPress, TQEvent::MouseButtonRelease, TQEvent::MouseButtonDblClick or TQEvent::MouseMove.
.PP
The \fIpos\fR parameter specifies the position relative to the receiving widget. \fIbutton\fR specifies the button that caused the event, which should be TQt::NoButton (0), if \fItype\fR is MouseMove. \fIstate\fR is the ButtonState at the time of the event.
.PP
@ -88,7 +88,7 @@ The globalPos() is initialized to QCursor::pos(), which may not be appropriate.
.SH "QMouseEvent::QMouseEvent ( Type type, const TQPoint & pos, const TQPoint & globalPos, int button, int state )"
Constructs a mouse event object.
.PP
The \fItype\fR parameter must be QEvent::MouseButtonPress, QEvent::MouseButtonRelease, QEvent::MouseButtonDblClick or QEvent::MouseMove.
The \fItype\fR parameter must be TQEvent::MouseButtonPress, TQEvent::MouseButtonRelease, TQEvent::MouseButtonDblClick or TQEvent::MouseMove.
.PP
The \fIpos\fR parameter specifies the position relative to the receiving widget. \fIglobalPos\fR is the position in absolute coordinates. \fIbutton\fR specifies the button that caused the event, which should be TQt::NoButton (0), if \fItype\fR is MouseMove. \fIstate\fR is the ButtonState at the time of the event.
.SH "void QMouseEvent::accept ()"
@ -146,9 +146,9 @@ Examples:
.SH "ButtonState QMouseEvent::state () const"
Returns the button state (a combination of mouse buttons and keyboard modifiers), i.e. what buttons and keys were being pressed immediately before the event was generated.
.PP
This means that if you have a QEvent::MouseButtonPress or a QEvent::MouseButtonDblClick state() will \fInot\fR include the mouse button that's pressed. But once the mouse button has been released, the QEvent::MouseButtonRelease event will have the button() that was pressed.
This means that if you have a TQEvent::MouseButtonPress or a TQEvent::MouseButtonDblClick state() will \fInot\fR include the mouse button that's pressed. But once the mouse button has been released, the TQEvent::MouseButtonRelease event will have the button() that was pressed.
.PP
This value is mainly interesting for QEvent::MouseMove; for the other cases, button() is more useful.
This value is mainly interesting for TQEvent::MouseMove; for the other cases, button() is more useful.
.PP
The returned value is LeftButton, RightButton, MidButton, ShiftButton, ControlButton and AltButton OR'ed together.
@ -259,7 +259,7 @@ This event handler can be reimplemented in a subclass to receive child events.
.PP
Child events are sent to objects when children are inserted or removed.
.PP
Note that events with QEvent::type() QEvent::ChildInserted are posted (with QApplication::postEvent()) to make sure that the child's construction is completed before this function is called.
Note that events with TQEvent::type() TQEvent::ChildInserted are posted (with QApplication::postEvent()) to make sure that the child's construction is completed before this function is called.
.PP
If a child is removed immediately after it is inserted, the \fCChildInserted\fR event may be suppressed, but the \fCChildRemoved\fR event will always be sent. In such cases it is possible that there will be a \fCChildRemoved\fR event without a corresponding \fCChildInserted\fR event.
.PP
@ -267,7 +267,7 @@ If you change state based on \fCChildInserted\fR events, call TQWidget::constPol
This event handler can be reimplemented in a subclass to receive custom events. Custom events are user-defined events with a type value at least as large as the "User" item of the QEvent::Type enum, and is typically a QCustomEvent or QCustomEvent subclass.
This event handler can be reimplemented in a subclass to receive custom events. Custom events are user-defined events with a type value at least as large as the "User" item of the TQEvent::Type enum, and is typically a QCustomEvent or QCustomEvent subclass.
.PP
See also event() and QCustomEvent.
.SH "void TQObject::deleteLater ()\fC [slot]\fR"
@ -492,7 +492,7 @@ This function is useful for debugging, but does nothing if the library has been
Dumps a tree of children to the debug output.
.PP
This function is useful for debugging, but does nothing if the library has been compiled in release mode (i.e. without debugging information).
.SH "bool TQObject::event ( QEvent * e )\fC [virtual]\fR"
.SH "bool TQObject::event ( TQEvent * e )\fC [virtual]\fR"
This virtual function receives events to an object and should return TRUE if the event \fIe\fR was recognized and processed.
.PP
The event() function can be reimplemented to customize the behavior of an object.
@ -500,7 +500,7 @@ The event() function can be reimplemented to customize the behavior of an object
See also installEventFilter(), timerEvent(), QApplication::sendEvent(), QApplication::postEvent(), and TQWidget::event().
Filters events if this object has been installed as an event filter for the \fIwatched\fR object.
.PP
In your reimplementation of this function, if you want to filter the event \fIe\fR, out, i.e. stop it being handled further, return TRUE; otherwise return FALSE.
@ -149,7 +149,7 @@ The dialog automatically resets and hides itself at the end of the operation. Us
.PP
There are two ways of using QProgressDialog: modal and modeless.
.PP
Using a modal QProgressDialog is simpler for the programmer, but you must call QApplication::processEvents() or QEventLoop::processEvents(ExcludeUserInput) to keep the event loop running to ensure that the application doesn't freeze. Do the operation in a loop, call setProgress() at intervals, and check for cancellation with wasCanceled(). For example:
Using a modal QProgressDialog is simpler for the programmer, but you must call QApplication::processEvents() or TQEventLoop::processEvents(ExcludeUserInput) to keep the event loop running to ensure that the application doesn't freeze. Do the operation in a loop, call setProgress() at intervals, and check for cancellation with wasCanceled(). For example:
@ -656,7 +656,7 @@ Scrolls the content so that the point \fI(x, y)\fR is visible with at least 50-p
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Scrolls the content so that the point \fI(x, y)\fR is visible with at least the \fIxmargin\fR and \fIymargin\fR margins (if possible, otherwise centered).
This event filter ensures the scroll bars are updated when a single contents widget is resized, shown, hidden or destroyed; it passes mouse events to the QScrollView. The event is in \fIe\fR and the object is in \fIobj\fR.
.SH "bool QSpinBox::eventFilter ( TQObject * o, QEvent * ev )\fC [virtual protected]\fR"
.SH "bool QSpinBox::eventFilter ( TQObject * o, TQEvent * ev )\fC [virtual protected]\fR"
Intercepts and handles the events coming to the embedded QLineEdit that have special meaning for the QSpinBox. The object is passed as \fIo\fR and the event is passed as \fIev\fR.
The QTranslator class provides internationalization support for text output.
The TQTranslator class provides internationalization support for text output.
.PP
An object of this class contains a set of QTranslatorMessage objects, each of which specifies a translation from a source language to a target language. QTranslator provides functions to look up translations, add new ones, remove them, load and save them, etc.
An object of this class contains a set of TQTranslatorMessage objects, each of which specifies a translation from a source language to a target language. TQTranslator provides functions to look up translations, add new ones, remove them, load and save them, etc.
.PP
The most common use of QTranslator is to: load a translator file created with TQt Linguist, install it using QApplication::installTranslator(), and use it via TQObject::tr(). For example:
The most common use of TQTranslator is to: load a translator file created with TQt Linguist, install it using QApplication::installTranslator(), and use it via TQObject::tr(). For example:
.PP
.nf
.br
@ -86,7 +86,7 @@ The most common use of QTranslator is to: load a translator file created with TQ
QApplication app( argc, argv );
.br
.br
QTranslator translator( 0 );
TQTranslator translator( 0 );
.br
translator.load( "french.qm", "." );
.br
@ -113,7 +113,7 @@ We call a translation a "messsage". For this reason, translation files are somet
.PP
It is possible to lookup a translation using findMessage() (as tr() and QApplication::translate() do) and contains(), to insert a new translation messsage using insert(), and to remove one using remove().
.PP
Translation tools often need more information than the bare source text and translation, for example, context information to help the translator. But end-user programs that are using translations usually only need lookup. To cater for these different needs, QTranslator can use stripped translator files that use the minimum of memory and which support little more functionality than findMessage().
Translation tools often need more information than the bare source text and translation, for example, context information to help the translator. But end-user programs that are using translations usually only need lookup. To cater for these different needs, TQTranslator can use stripped translator files that use the minimum of memory and which support little more functionality than findMessage().
.PP
Thus, load() may not load enough information to make anything more than findMessage() work. save() has an argument indicating whether to save just this minimum of information or to save everything.
.PP"
@ -135,54 +135,54 @@ For example, the "Cancel" in a dialog might have "Anuluj" when the program runs
.PP
But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would probably require both "Activado" and "Activada" as translations for "Enabled". In this case the source text would be "Enabled" in both cases, and the context would be the dialog's class name, but the two items would have disambiguating comments such as" two-sided printing" for one and "binding" for the other. The comment enables the translator to choose the appropriate gender for the Spanish version, and enables TQt to distinguish between translations.
.PP
Note that when QTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
Note that when TQTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
.PP
See also QTranslatorMessage, QApplication::installTranslator(), QApplication::removeTranslator(), TQObject::tr(), QApplication::translate(), Environment Classes, and Internationalization with Qt.
See also TQTranslatorMessage, QApplication::installTranslator(), QApplication::removeTranslator(), TQObject::tr(), QApplication::translate(), Environment Classes, and Internationalization with Qt.
.SS "Member Type Documentation"
.SH "QTranslator::SaveMode"
This enum type defines how QTranslator writes translation files. There are two modes:
.SH "TQTranslator::SaveMode"
This enum type defines how TQTranslator writes translation files. There are two modes:
.TP
\fCQTranslator::Everything\fR - files are saved with all available information
\fCTQTranslator::Everything\fR - files are saved with all available information
.TP
\fCQTranslator::Stripped\fR - files are saved with just enough information for end-user applications
\fCTQTranslator::Stripped\fR - files are saved with just enough information for end-user applications
.PP
Note that when QTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
Note that when TQTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
Returns the QTranslatorMessage for the key (\fIcontext\fR, \fIsourceText\fR, \fIcomment\fR). If none is found, also tries (\fIcontext\fR, \fIsourceText\fR, "").
Returns the TQTranslatorMessage for the key (\fIcontext\fR, \fIsourceText\fR, \fIcomment\fR). If none is found, also tries (\fIcontext\fR, \fIsourceText\fR, "").
Loads \fIfilename\fR, which may be an absolute file name or relative to \fIdirectory\fR. The previous contents of this translator object is discarded. Returns TRUE if the file is loaded successfully; otherwise returns FALSE.
.PP
If the full file name does not exist, other file names are tried in the following order:
@ -216,22 +216,22 @@ For example, an application running in the fr_CA locale (French-speaking Canada)
See also save().
.PP
Example: i18n/main.cpp.
.SH "bool QTranslator::load ( const uchar * data, int len )"
.SH "bool TQTranslator::load ( const uchar * data, int len )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Loads the .qm file data \fIdata\fR of length \fIlen\fR into the translator. Returns TRUE if the data is loaded successfully; otherwise returns FALSE.
.PP
The data is not copied. The caller must be able to guarantee that \fIdata\fR will not be deleted or modified.
Returns a list of the messages in the translator. This function is rather slow. Because it is seldom called, it's optimized for simplicity and small size, rather than speed.
.PP
If you want to iterate over the list, you should iterate over a copy, e.g.
.PP
.nf
.br
TQValueList<QTranslatorMessage> list = myTranslator.messages();
TQValueList<TQTranslatorMessage> list = myTranslator.messages();
.br
TQValueList<QTranslatorMessage>::Iterator it = list.begin();
TQValueList<TQTranslatorMessage>::Iterator it = list.begin();
.br
while ( it != list.end() ) {
.br
@ -242,29 +242,29 @@ If you want to iterate over the list, you should iterate over a copy, e.g.
Saves this message file to \fIfilename\fR, overwriting the previous contents of \fIfilename\fR. If \fImode\fR is Everything (the default), all the information is preserved. If \fImode\fR is Stripped, any information that is not necessary for findMessage() is stripped away.
.BI "Prefix \fBcommonPrefix\fR ( const QTranslatorMessage & m ) const"
.BI "Prefix \fBcommonPrefix\fR ( const TQTranslatorMessage & m ) const"
.br
.ti -1c
.BI "bool \fBoperator==\fR ( const QTranslatorMessage & m ) const"
.BI "bool \fBoperator==\fR ( const TQTranslatorMessage & m ) const"
.br
.ti -1c
.BI "bool \fBoperator!=\fR ( const QTranslatorMessage & m ) const"
.BI "bool \fBoperator!=\fR ( const TQTranslatorMessage & m ) const"
.br
.ti -1c
.BI "bool \fBoperator<\fR ( const QTranslatorMessage & m ) const"
.BI "bool \fBoperator<\fR ( const TQTranslatorMessage & m ) const"
.br
.ti -1c
.BI "bool \fBoperator<=\fR ( const QTranslatorMessage & m ) const"
.BI "bool \fBoperator<=\fR ( const TQTranslatorMessage & m ) const"
.br
.ti -1c
.BI "bool \fBoperator>\fR ( const QTranslatorMessage & m ) const"
.BI "bool \fBoperator>\fR ( const TQTranslatorMessage & m ) const"
.br
.ti -1c
.BI "bool \fBoperator>=\fR ( const QTranslatorMessage & m ) const"
.BI "bool \fBoperator>=\fR ( const TQTranslatorMessage & m ) const"
.br
.in -1c
.SH DESCRIPTION
The QTranslatorMessage class contains a translator message and its properties.
The TQTranslatorMessage class contains a translator message and its properties.
.PP
This class is of no interest to most applications. It is useful for translation tools such as TQt Linguist. It is provided simply to make the API complete and regular.
.PP
For a QTranslator object, a lookup key is a triple (\fIcontext\fR, \fIsource text\fR, \fIcomment\fR) that uniquely identifies a message. An extended key is a quadruple (\fIhash\fR, \fIcontext\fR, \fIsource text\fR, \fIcomment\fR), where \fIhash\fR is computed from the source text and the comment. Unless you plan to read and write messages yourself, you need not worry about the hash value.
For a TQTranslator object, a lookup key is a triple (\fIcontext\fR, \fIsource text\fR, \fIcomment\fR) that uniquely identifies a message. An extended key is a quadruple (\fIhash\fR, \fIcontext\fR, \fIsource text\fR, \fIcomment\fR), where \fIhash\fR is computed from the source text and the comment. Unless you plan to read and write messages yourself, you need not worry about the hash value.
.PP
QTranslatorMessage stores this triple or quadruple and the relevant translation if there is any.
TQTranslatorMessage stores this triple or quadruple and the relevant translation if there is any.
.PP
See also QTranslator, Environment Classes, and Internationalization with Qt.
See also TQTranslator, Environment Classes, and Internationalization with Qt.
.SS "Member Type Documentation"
.SH "QTranslatorMessage::Prefix"
.SH "TQTranslatorMessage::Prefix"
Let (\fIh\fR, \fIc\fR, \fIs\fR, \fIm\fR) be the extended key. The possible prefixes are
.TP
\fCQTranslatorMessage::NoPrefix\fR - no prefix
\fCTQTranslatorMessage::NoPrefix\fR - no prefix
.TP
\fCQTranslatorMessage::Hash\fR - only (\fIh\fR)
\fCTQTranslatorMessage::Hash\fR - only (\fIh\fR)
.TP
\fCQTranslatorMessage::HashContext\fR - only (\fIh\fR, \fIc\fR)
\fCTQTranslatorMessage::HashContext\fR - only (\fIh\fR, \fIc\fR)
.TP
\fCQTranslatorMessage::HashContextSourceText\fR - only (\fIh\fR, \fIc\fR, \fIs\fR)
\fCTQTranslatorMessage::HashContextSourceText\fR - only (\fIh\fR, \fIc\fR, \fIs\fR)
.TP
\fCQTranslatorMessage::HashContextSourceTextComment\fR - the whole extended key, (\fIh\fR, \fIc\fR, \fIs\fR, \fIm\fR)
\fCTQTranslatorMessage::HashContextSourceTextComment\fR - the whole extended key, (\fIh\fR, \fIc\fR, \fIs\fR, \fIm\fR)
.PP
See also write() and commonPrefix().
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QTranslatorMessage::QTranslatorMessage ()"
.SH "TQTranslatorMessage::TQTranslatorMessage ()"
Constructs a translator message with the extended key (0, 0, 0, 0) and TQString::null as translation.
Constructs an translator message with the extended key (\fIh\fR, \fIcontext\fR, \fIsourceText\fR, \fIcomment\fR), where \fIh\fR is computed from \fIsourceText\fR and \fIcomment\fR, and possibly with a \fItranslation\fR.
Returns the comment for this message (e.g. "File|Save").
.PP
\fBWarning:\fR This may return 0 if the QTranslator object is stripped (compressed).
.SH "Prefix QTranslatorMessage::commonPrefix ( const QTranslatorMessage & m ) const"
\fBWarning:\fR This may return 0 if the TQTranslator object is stripped (compressed).
.SH "Prefix TQTranslatorMessage::commonPrefix ( const TQTranslatorMessage & m ) const"
Returns the widest lookup prefix that is common to this translator message and to message \fIm\fR.
.PP
For example, if the extended key is for this message is (71," PrintDialog", "Yes", "Print?") and that for \fIm\fR is (71," PrintDialog", "No", "Print?"), this function returns HashContext.
Returns the context for this message (e.g. "MyDialog").
.PP
\fBWarning:\fR This may return 0 if the QTranslator object is stripped (compressed).
.SH "uint QTranslatorMessage::hash () const"
\fBWarning:\fR This may return 0 if the TQTranslator object is stripped (compressed).
.SH "uint TQTranslatorMessage::hash () const"
Returns the hash value used internally to represent the lookup key. This value is zero only if this translator message was constructed from a stream containing invalid data.
.PP
The hashing function is unspecified, but it will remain unchanged in future versions of Qt.
.SH "bool QTranslatorMessage::operator!= ( const QTranslatorMessage & m ) const"
.SH "bool TQTranslatorMessage::operator!= ( const TQTranslatorMessage & m ) const"
Returns TRUE if the extended key of this object is different from that of \fIm\fR; otherwise returns FALSE.
.SH "bool QTranslatorMessage::operator< ( const QTranslatorMessage & m ) const"
.SH "bool TQTranslatorMessage::operator< ( const TQTranslatorMessage & m ) const"
Returns TRUE if the extended key of this object is lexicographically before than that of \fIm\fR; otherwise returns FALSE.
.SH "bool QTranslatorMessage::operator<= ( const QTranslatorMessage & m ) const"
.SH "bool TQTranslatorMessage::operator<= ( const TQTranslatorMessage & m ) const"
Returns TRUE if the extended key of this object is lexicographically before that of \fIm\fR or if they are equal; otherwise returns FALSE.
.SH "QTranslatorMessage & QTranslatorMessage::operator= ( const QTranslatorMessage & m )"
.SH "TQTranslatorMessage & TQTranslatorMessage::operator= ( const TQTranslatorMessage & m )"
Assigns message \fIm\fR to this translator message and returns a reference to this translator message.
.SH "bool QTranslatorMessage::operator== ( const QTranslatorMessage & m ) const"
.SH "bool TQTranslatorMessage::operator== ( const TQTranslatorMessage & m ) const"
Returns TRUE if the extended key of this object is equal to that of \fIm\fR; otherwise returns FALSE.
.SH "bool QTranslatorMessage::operator> ( const QTranslatorMessage & m ) const"
.SH "bool TQTranslatorMessage::operator> ( const TQTranslatorMessage & m ) const"
Returns TRUE if the extended key of this object is lexicographically after that of \fIm\fR; otherwise returns FALSE.
.SH "bool QTranslatorMessage::operator>= ( const QTranslatorMessage & m ) const"
.SH "bool TQTranslatorMessage::operator>= ( const TQTranslatorMessage & m ) const"
Returns TRUE if the extended key of this object is lexicographically after that of \fIm\fR or if they are equal; otherwise returns FALSE.
Writes this translator message to the \fIstream\fR. If \fIstrip\fR is FALSE (the default), all the information in the message is written. If \fIstrip\fR is TRUE, only the part of the extended key specified by \fIprefix\fR is written with the translation (HashContextSourceTextComment by default).
@ -1087,7 +1087,7 @@ moveEvent() - called when the widget has been moved relative to its parent.
closeEvent() - called when the user closes the widget (or when close() is called).
.IP
.PP
There are also some rather obscure events. They are listed in ntqevent.h and you need to reimplement event() to handle them. The default implementation of event() handles Tab and Shift+Tab (to move the keyboard focus), and passes on most other events to one of the more specialized handlers above.
There are also some rather obscure events. They are listed in tqevent.h and you need to reimplement event() to handle them. The default implementation of event() handles Tab and Shift+Tab (to move the keyboard focus), and passes on most other events to one of the more specialized handlers above.
.PP
When implementing a widget, there are a few more things to consider.
.IP
@ -1101,7 +1101,7 @@ It is almost always useful to reimplement sizeHint() and to set the correct size
If your widget is a top-level window, setCaption() and setIcon() set the title bar and icon respectively.
.IP
.PP
See also QEvent, TQPainter, QGridLayout, QBoxLayout, and Abstract Widget Classes.
See also TQEvent, TQPainter, QGridLayout, QBoxLayout, and Abstract Widget Classes.
.SS "Member Type Documentation"
.SH "TQWidget::BackgroundOrigin"
This enum defines the origin used to draw a widget's background pixmap.
@ -1338,7 +1338,7 @@ Reimplement this function if your widget needs to know when it becomes enabled o
The default implementation repaints the visible part of the widget.
.PP
See also enabled, enabled, repaint(), update(), and clipRegion().
This event handler can be reimplemented in a subclass to receive widget enter events.
.PP
An event is sent to the widget when the mouse cursor enters the widget.
@ -1374,7 +1374,7 @@ See also setEraseColor(), setErasePixmap(), and backgroundColor().
Returns the widget's erase pixmap.
.PP
See also setErasePixmap() and eraseColor().
.SH "bool TQWidget::event ( QEvent * e )\fC [virtual protected]\fR"
.SH "bool TQWidget::event ( TQEvent * e )\fC [virtual protected]\fR"
This is the main event handler; it handles event \fIe\fR. You can reimplement this function in a subclass, but we recommend using one of the specialized event handlers instead.
.PP
The main event handler first passes an event through all event filters that have been installed. If none of the filters intercept the event, it calls one of the specialized event handlers.
@ -1655,7 +1655,7 @@ See also sizePolicy.
.PP
Examples:
.)l chart/optionsform.cpp and fonts/simple-tqfont-demo/viewer.cpp.
