<trbgcolor=#f0f0f0><td><b><ahref="ntqaccel.html">TQAccel</a></b><td>Handles keyboard accelerator and shortcut keys
<trbgcolor=#f0f0f0><td><b><ahref="ntqaccessible.html">TQAccessible</a></b><td>Enums and static functions relating to accessibility
<trbgcolor=#f0f0f0><td><b><ahref="qaccessibleinterface.html">TQAccessibleInterface</a></b><td>Defines an interface that exposes information about accessible objects
<trbgcolor=#f0f0f0><td><b><ahref="qaccessibleobject.html">TQAccessibleObject</a></b><td>Implements parts of the TQAccessibleInterface for TQObjects
<trbgcolor=#f0f0f0><td><b><ahref="tqaccel.html">TQAccel</a></b><td>Handles keyboard accelerator and shortcut keys
<trbgcolor=#f0f0f0><td><b><ahref="tqaccessible.html">TQAccessible</a></b><td>Enums and static functions relating to accessibility
<trbgcolor=#f0f0f0><td><b><ahref="tqaccessibleinterface.html">TQAccessibleInterface</a></b><td>Defines an interface that exposes information about accessible objects
<trbgcolor=#f0f0f0><td><b><ahref="tqaccessibleobject.html">TQAccessibleObject</a></b><td>Implements parts of the TQAccessibleInterface for TQObjects
<trbgcolor=#f0f0f0><td><b><ahref="tqaction.html">TQAction</a></b><td>Abstract user interface action that can appear both in menus and tool bars
<trbgcolor=#f0f0f0><td><b><ahref="tqactiongroup.html">TQActionGroup</a></b><td>Groups actions together
<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="tqbutton.html">TQButton</a></b><td>The abstract base class of button widgets, providing functionality common to buttons
<trbgcolor=#f0f0f0><td><b><ahref="tqbuttongroup.html">TQButtonGroup</a></b><td>Organizes TQButton widgets in a group
<trbgcolor=#f0f0f0><td><b><ahref="tqbytearray.html">TQByteArray</a></b><td>Array of bytes
<trbgcolor=#f0f0f0><td><b><ahref="ntqcdestyle.html">TQCDEStyle</a></b><td>CDE look and feel
<trbgcolor=#f0f0f0><td><b><ahref="tqcdestyle.html">TQCDEStyle</a></b><td>CDE look and feel
<trbgcolor=#f0f0f0><td><b><ahref="tqcstring.html">TQCString</a></b><td>Abstraction of the classic C zero-terminated char array (char *)
<trbgcolor=#f0f0f0><td><b><ahref="tqcache.html">TQCache</a></b><td>Template class that provides a cache based on TQString keys
<trbgcolor=#f0f0f0><td><b><ahref="tqcacheiterator.html">TQCacheIterator</a></b><td>Iterator for TQCache collections
<trbgcolor=#f0f0f0><td><b><ahref="qmetaproperty.html">TQMetaProperty</a></b><td>Stores meta data about a property
<trbgcolor=#f0f0f0><td><b><ahref="tqmimesource.html">TQMimeSource</a></b><td>Abstraction of objects which provide formatted data of a certain MIME type
<trbgcolor=#f0f0f0><td><b><ahref="tqmimesourcefactory.html">TQMimeSourceFactory</a></b><td>Extensible provider of mime-typed data
<trbgcolor=#f0f0f0><td><b><ahref="qmotif.html">TQMotif</a></b><td>The basis of the <ahref="motif-extension.html#Motif">Motif</a> Extension
<trbgcolor=#f0f0f0><td><b><ahref="qmotifdialog.html">TQMotifDialog</a></b><td>The TQDialog API for Motif-based dialogs
<trbgcolor=#f0f0f0><td><b><ahref="ntqmotifplusstyle.html">TQMotifPlusStyle</a></b><td>More sophisticated Motif-ish look and feel
<trbgcolor=#f0f0f0><td><b><ahref="ntqmotifstyle.html">TQMotifStyle</a></b><td>Motif look and feel
<trbgcolor=#f0f0f0><td><b><ahref="qmotifwidget.html">TQMotifWidget</a></b><td>The TQWidget API for Xt/Motif widgets
<trbgcolor=#f0f0f0><td><b><ahref="tqmotif.html">TQMotif</a></b><td>The basis of the <ahref="motif-extension.html#Motif">Motif</a> Extension
<trbgcolor=#f0f0f0><td><b><ahref="tqmotifdialog.html">TQMotifDialog</a></b><td>The TQDialog API for Motif-based dialogs
<trbgcolor=#f0f0f0><td><b><ahref="tqmotifplusstyle.html">TQMotifPlusStyle</a></b><td>More sophisticated Motif-ish look and feel
<trbgcolor=#f0f0f0><td><b><ahref="tqmotifstyle.html">TQMotifStyle</a></b><td>Motif look and feel
<trbgcolor=#f0f0f0><td><b><ahref="tqmotifwidget.html">TQMotifWidget</a></b><td>The TQWidget API for Xt/Motif widgets
<trbgcolor=#f0f0f0><td><b><ahref="qmouseevent.html">TQMouseEvent</a></b><td>Parameters that describe a mouse event
<trbgcolor=#f0f0f0><td><b><ahref="qmoveevent.html">TQMoveEvent</a></b><td>Event parameters for move events
<trbgcolor=#f0f0f0><td><b><ahref="tqmovie.html">TQMovie</a></b><td>Incremental loading of animations or images, signalling as it progresses
<trbgcolor=#f0f0f0><td><b><ahref="tqregexpvalidator.html">TQRegExpValidator</a></b><td>Used to check a string against a <ahref="tqregexp.html#regular-expression">regular expression</a>
<trbgcolor=#f0f0f0><td><b><ahref="tqregion.html">TQRegion</a></b><td>Clip region for a painter
<trbgcolor=#f0f0f0><td><b><ahref="qresizeevent.html">TQResizeEvent</a></b><td>Event parameters for resize events
<trbgcolor=#f0f0f0><td><b><ahref="ntqsgistyle.html">TQSGIStyle</a></b><td>SGI/Irix look and feel
<trbgcolor=#f0f0f0><td><b><ahref="tqsgistyle.html">TQSGIStyle</a></b><td>SGI/Irix look and feel
<trbgcolor=#f0f0f0><td><b><ahref="tqscrollbar.html">TQScrollBar</a></b><td>Vertical or horizontal scroll bar
<trbgcolor=#f0f0f0><td><b><ahref="tqscrollview.html">TQScrollView</a></b><td>Scrolling area with on-demand scroll bars
<p>If we left this code as-is, the user could by-pass our own termination code by clicking the main window's close (X) button. Since we want to give the user the option to save any unsaved changes we need to ensure that we intercept any attempt to close the application. To achieve this we delete the connection and add a new slot, <tt>closeEvent()</tt> which will intercept attempts to close the application and call our <tt>fileExit()</tt> function.</p>
<p>Click <tt>main.cpp</tt> in the Project Overview window. The file will appear in an editing window. Delete the connect line.</p>
<p>Click <tt>mainform.ui.h</tt> in the Project Overview window; (you may need to click <tt>mainform.ui</tt> first to reveal <tt>mainform.ui.h</tt>). Right click "fileExit()" in Object Explorer's Members list (under Slots, public), then click <b>Goto Implementation</b>. Add the following slot above the <tt>fileExit()</tt> slot:</p>
and <ahref="signalsandslots.html">Signals and Slots</a>.
<p><tablewidth="100%">
<trbgcolor=#f0f0f0><td><b><ahref="qchildevent.html">TQChildEvent</a></b><td>Event parameters for child object events
<trbgcolor=#f0f0f0><td><b><ahref="qcloseevent.html">TQCloseEvent</a></b><td>Parameters that describe a close event
<trbgcolor=#f0f0f0><td><b><ahref="qcontextmenuevent.html">TQContextMenuEvent</a></b><td>Parameters that describe a context menu event
<trbgcolor=#f0f0f0><td><b><ahref="qcustomevent.html">TQCustomEvent</a></b><td>Support for custom events
<trbgcolor=#f0f0f0><td><b><ahref="tqchildevent.html">TQChildEvent</a></b><td>Event parameters for child object events
<trbgcolor=#f0f0f0><td><b><ahref="tqcloseevent.html">TQCloseEvent</a></b><td>Parameters that describe a close event
<trbgcolor=#f0f0f0><td><b><ahref="tqcontextmenuevent.html">TQContextMenuEvent</a></b><td>Parameters that describe a context menu event
<trbgcolor=#f0f0f0><td><b><ahref="tqcustomevent.html">TQCustomEvent</a></b><td>Support for custom events
<trbgcolor=#f0f0f0><td><b><ahref="tqdragenterevent.html">TQDragEnterEvent</a></b><td>Event which is sent to the widget when a drag and drop first drags onto the widget
<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
@ -45,7 +45,7 @@ from other sources, e.g. <a href="tqtimerevent.html">TQTimerEvent</a>, and some
application program. TQt is symmetric, as usual, so you can send
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>.
<ahref="tqpaintevent.html">TQPaintEvent</a>, <ahref="qmouseevent.html">TQMouseEvent</a>, <ahref="qkeyevent.html">TQKeyEvent</a> and <ahref="tqcloseevent.html">TQCloseEvent</a>.
There are many others, perhaps forty or so, but most are rather odd.
<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.
@ -94,7 +94,7 @@ contain:
return TRUE;
}
} else if ( evt-><ahref="tqevent.html#type">type</a>() >= TQEvent::User ) {
<p> These classes are useful classes not fitting into any other category.
<p>
<p><tablewidth="100%">
<trbgcolor=#f0f0f0><td><b><ahref="ntqaccel.html">TQAccel</a></b><td>Handles keyboard accelerator and shortcut keys
<trbgcolor=#f0f0f0><td><b><ahref="ntqaccessible.html">TQAccessible</a></b><td>Enums and static functions relating to accessibility
<trbgcolor=#f0f0f0><td><b><ahref="qaccessibleinterface.html">TQAccessibleInterface</a></b><td>Defines an interface that exposes information about accessible objects
<trbgcolor=#f0f0f0><td><b><ahref="qaccessibleobject.html">TQAccessibleObject</a></b><td>Implements parts of the TQAccessibleInterface for TQObjects
<trbgcolor=#f0f0f0><td><b><ahref="qcustommenuitem.html">TQCustomMenuItem</a></b><td>Abstract base class for custom menu items in popup menus
<trbgcolor=#f0f0f0><td><b><ahref="tqaccel.html">TQAccel</a></b><td>Handles keyboard accelerator and shortcut keys
<trbgcolor=#f0f0f0><td><b><ahref="tqaccessible.html">TQAccessible</a></b><td>Enums and static functions relating to accessibility
<trbgcolor=#f0f0f0><td><b><ahref="tqaccessibleinterface.html">TQAccessibleInterface</a></b><td>Defines an interface that exposes information about accessible objects
<trbgcolor=#f0f0f0><td><b><ahref="tqaccessibleobject.html">TQAccessibleObject</a></b><td>Implements parts of the TQAccessibleInterface for TQObjects
<trbgcolor=#f0f0f0><td><b><ahref="tqcustommenuitem.html">TQCustomMenuItem</a></b><td>Abstract base class for custom menu items in popup menus
<trbgcolor=#f0f0f0><td><b><ahref="qdoublevalidator.html">TQDoubleValidator</a></b><td>Range checking of floating-point numbers
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>TQMotif Support Extension</h1>
<p> The following example programs illustrate the use of the <ahref="qmotif.html">TQMotif</a> Extension
<p> The following example programs illustrate the use of the <ahref="tqmotif.html">TQMotif</a> Extension
assisting in the migration process of old Xt and <ahref="motif-extension.html#Motif">Motif</a> based code
to the more comfortable TQt toolkit.
<p> For more information see the <ahref="motif-extension.html">TQMotif
<aname="2-3"></a><p><ahref="qmotifwidget.html">TQMotifWidget</a> can be used together with <ahref="tqdesktopwidget.html">TQDesktopWidget</a> to create
<aname="2-3"></a><p><ahref="tqmotifwidget.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
to both TQMotifWidget and the Xt/Motif child. For example:
@ -48,7 +48,7 @@ provide useful static convenience functions.
<p> Each of these functions takes a <em>TQWidget *parent</em> argument. If we
pass zero as the <em>parent</em> argument, then we will have dialogs that
are centered on the screen, instead of being centered over our main
window. We can have <ahref="qmotifwidget.html">TQMotifWidget</a> create our <tt>XmMainWindow</tt>, and we
window. We can have <ahref="tqmotifwidget.html">TQMotifWidget</a> create our <tt>XmMainWindow</tt>, and we
can then use this class as the parent for both <ahref="motif-extension.html#Motif">Motif</a> dialogs and TQt
dialogs.
<p> We need to include the appropriate headers for TQMotifWidget and
@ -57,9 +57,9 @@ dialogs.
<pre></pre>
<p> Next, we make a few modifications to how the application is
initialized. We could initialize Xt/Motif and create the <tt>XtAppContext</tt> ourselves, but <ahref="qmotif.html">TQMotif</a> can do this for us.
initialized. We could initialize Xt/Motif and create the <tt>XtAppContext</tt> ourselves, but <ahref="tqmotif.html">TQMotif</a> can do this for us.
We also let <ahref="ntqapplication.html">TQApplication</a> open the connection to the X server. Next,
we create a TQMotifWidget, passing <tt>xmMainWindowWidgetClass</tt> as the <em>widgetclass</em> argument. We can now use the <ahref="qmotifwidget.html#motifWidget">TQMotifWidget::motifWidget</a>()
we create a TQMotifWidget, passing <tt>xmMainWindowWidgetClass</tt> as the <em>widgetclass</em> argument. We can now use the <ahref="tqmotifwidget.html#motifWidget">TQMotifWidget::motifWidget</a>()
function to access the Motif widget. The shell widget is created
automatically by TQMotifWidget. We use <tt>XtParent()</tt> to access it.
The top-level window is now a TQMotifWidget, which means we can use it
@ -79,7 +79,7 @@ and <tt>Save()</tt> functions.
<p><pre></pre>
<p> We also change the arguments to the callbacks. We pass the top-level
<ahref="qmotifwidget.html">TQMotifWidget</a> as the <tt>client_data</tt> to these functions, since we will
<ahref="tqmotifwidget.html">TQMotifWidget</a> as the <tt>client_data</tt> to these functions, since we will
be using it as the parent for the TQFileDialog.
<p><pre></pre>
<p><pre>
@ -123,7 +123,7 @@ the correct symbols for these functions.
<p> At this point in the code, the page should be deleted. The code to do
this is in the <tt>DoDeletePage()</tt> function. We move the contents of <tt>DoDeletePage()</tt> to this point and remove the <tt>DoDeletePage()</tt> function
completely.
<p> Next, we change <tt>todo.cpp</tt> to pass the top-level <ahref="qmotifwidget.html">TQMotifWidget</a> as the
<p> Next, we change <tt>todo.cpp</tt> to pass the top-level <ahref="tqmotifwidget.html">TQMotifWidget</a> as the
<tt>client_data</tt> tot he <tt>DeletePage()</tt> function.
@ -41,7 +41,7 @@ have converted the <em>View</em> widget. The <em>Print</em> dialog will be
removed once we have finished our migration, since we will use
<ahref="tqprinter.html">TQPrinter</a> instead. Based on this information, we decide that it is not
worth replacing the <em>Print</em> dialog with a custom <ahref="tqdialog.html">TQDialog</a> replacement.
Instead, we will keep the <ahref="motif-extension.html#Motif">Motif</a> based dialog and use <ahref="qmotifdialog.html">TQMotifDialog</a> to
Instead, we will keep the <ahref="motif-extension.html#Motif">Motif</a> based dialog and use <ahref="tqmotifdialog.html">TQMotifDialog</a> to
integrate the dialog with the application.
<p><h2> Modality Requirements
</h2>
@ -74,7 +74,7 @@ function:
<p><pre></pre>
<p><h2> Integrating the <em>Print</em> Dialog
</h2>
<aname="2"></a><p> Now that the <em>Print</em> dialog has the appropriate <em>accept</em> and <em>reject</em> callbacks, we can use <ahref="qmotifdialog.html">TQMotifDialog</a>. First we need to include
<aname="2"></a><p> Now that the <em>Print</em> dialog has the appropriate <em>accept</em> and <em>reject</em> callbacks, we can use <ahref="tqmotifdialog.html">TQMotifDialog</a>. First we need to include
the TQMotifDialog header in <tt>todo.cpp</tt>.
<p>
@ -82,19 +82,19 @@ the TQMotifDialog header in <tt>todo.cpp</tt>.
<p> We add a <tt>ShowPrintDialog()</tt> function which will create and execute the
print dialog.
<p><pre></pre>
<p> We change the <em>Print</em> menu item callback to call the new <tt>ShowPrintDialog()</tt> function. We pass the top-level <ahref="qmotifwidget.html">TQMotifWidget</a>, which
<p> We change the <em>Print</em> menu item callback to call the new <tt>ShowPrintDialog()</tt> function. We pass the top-level <ahref="tqmotifwidget.html">TQMotifWidget</a>, which
we will use as the parent for the dialog.
<p><pre></pre>
<p> The <tt>ShowPrintDialog()</tt> function creates the <em>Print</em> dialog and
executes it. We use the <tt>XmdNprintCallback</tt> callback to accept the
dialog and the <tt>XmNcancelCallback</tt> callback to reject the dialog. We
can do this easily by using the <ahref="qmotifdialog.html#acceptCallback">TQMotifDialog::acceptCallback</a>() and
<ahref="qmotifdialog.html#rejectCallback">TQMotifDialog::rejectCallback</a>() functions, respectively. We also
can do this easily by using the <ahref="tqmotifdialog.html#acceptCallback">TQMotifDialog::acceptCallback</a>() and
<ahref="tqmotifdialog.html#rejectCallback">TQMotifDialog::rejectCallback</a>() functions, respectively. We also
ensure that the <em>print</em> callback continues to call the <tt>Print()</tt> function as before.
<p><pre></pre>
<p> After we build the project, the application runs and operates as
expected. There is no visual or behavioral difference, even though
the <em>Print</em> dialog is using <ahref="qmotifdialog.html">TQMotifDialog</a>.
the <em>Print</em> dialog is using <ahref="tqmotifdialog.html">TQMotifDialog</a>.
<p> [ <ahref="motif-walkthrough-4.html">Previous: Using Custom TQDialogs</a> ]
[ <ahref="motif-walkthrough.html">Home</a> ]
[ <ahref="motif-walkthrough-6.html">Next: Using TQt Main Window Classes</a> ]
@ -53,7 +53,7 @@ is then compiled and linked into our application.
add the implementation for our <em>Main Window</em> to this skeleton
implementation.
<p> We begin by adding the necessary includes for <ahref="ntqapplication.html">TQApplication</a>
and <ahref="qmotifwidget.html">TQMotifWidget</a>.
and <ahref="tqmotifwidget.html">TQMotifWidget</a>.
<p>
<p><pre></pre>
@ -103,7 +103,7 @@ needed.
<p> The <tt>QuitAppl()</tt> and <tt>manageCB()</tt> callbacks are not needed any more,
so we remove them. We do not need the global <tt>shell</tt> variable
either. We remove it and all references to it in the <tt>New()</tt>, <tt>Save()</tt> and <tt>Open()</tt> callbacks.
<p> In <tt>main()</tt>, we make the large changes. First, we use our new <tt>MainWindow</tt> instead of <ahref="qmotifwidget.html">TQMotifWidget</a> with <tt>XmMainWindow</tt>.
<p> In <tt>main()</tt>, we make the large changes. First, we use our new <tt>MainWindow</tt> instead of <ahref="tqmotifwidget.html">TQMotifWidget</a> with <tt>XmMainWindow</tt>.
<p> Now that we have implemented our new <em>View</em> widget, we need to remove
the old <ahref="motif-extension.html#Motif">Motif</a> based view widget from <tt>todo.cpp</tt>.
<p> Since we will not be using any Motif widgets, we remove all Motif <tt>#include</tt> statements, including <ahref="qmotifwidget-h.html">qmotifwidget.h</a>.
<p> Since we will not be using any Motif widgets, we remove all Motif <tt>#include</tt> statements, including <ahref="tqmotifwidget-h.html">tqmotifwidget.h</a>.
<p>
<pre></pre><pre></pre>
<p> We also remove the forward declarations of the <tt>ReadDB()</tt> function
and the <tt>notebook</tt>, <tt>textw</tt> and <tt>labelw</tt> global variables.
<p><pre></pre>
<p> Next, we remove the <tt>center</tt> widget, which uses <ahref="qmotifwidget.html">TQMotifWidget</a>. The <em>Main Window</em> widget and <em>View</em> widget are contained entirely in our
<p> Next, we remove the <tt>center</tt> widget, which uses <ahref="tqmotifwidget.html">TQMotifWidget</a>. The <em>Main Window</em> widget and <em>View</em> widget are contained entirely in our
<tt>MainWindow</tt> class, so no extra initialization is needed after
Sets the application override cursor to <em>cursor</em>.
<p> Application override cursors are intended for showing the user
@ -1501,7 +1501,7 @@ object is transferred to TQApplication, so TQApplication will delete
the style object on application exit or when a new style is set.
<p> Example usage:
<pre>
TQApplication::<ahref="#setStyle">setStyle</a>( new <ahref="ntqwindowsstyle.html">TQWindowsStyle</a> );
TQApplication::<ahref="#setStyle">setStyle</a>( new <ahref="tqwindowsstyle.html">TQWindowsStyle</a> );
</pre>
<p> When switching application styles, the color palette is set back to
@ -1680,7 +1680,7 @@ Returns a pointer to the widget at global screen position <em>(x, y)</em>, or 0
<p> If <em>child</em> is FALSE and there is a child widget at position <em>(x, y)</em>, the top-level widget containing it is returned. If <em>child</em>
is TRUE the child widget at position <em>(x, y)</em> is returned.
<p> This function is normally rather slow.
<p><p>See also <ahref="ntqcursor.html#pos">TQCursor::pos</a>(), <ahref="tqwidget.html#grabMouse">TQWidget::grabMouse</a>(), and <ahref="tqwidget.html#grabKeyboard">TQWidget::grabKeyboard</a>().
<p><p>See also <ahref="tqcursor.html#pos">TQCursor::pos</a>(), <ahref="tqwidget.html#grabMouse">TQWidget::grabMouse</a>(), and <ahref="tqwidget.html#grabKeyboard">TQWidget::grabKeyboard</a>().
@ -473,8 +473,7 @@ than the first two required parameters you will must add a value
for the <tt>echo</tt> parameter.
<p><h2><ahref="tqlayout.html">TQLayout</a> and Other Abstract Layout Classes
</h2>
<aname="12"></a><p> The definitions of <ahref="tqglayoutiterator.html">TQGLayoutIterator</a>, <ahref="tqlayout.html">TQLayout</a>, <ahref="tqlayoutitem.html">TQLayoutItem</a>, <ahref="tqlayoutiterator.html">TQLayoutIterator</a>, <ahref="tqspaceritem.html">TQSpacerItem</a> and <ahref="tqwidgetitem.html">TQWidgetItem</a> have been moved from <tt><ntqabstractlayout.h></tt> to <tt><tqlayout.h></tt>. The header <tt><ntqabstractlayout.h></tt> now includes <tt><tqlayout.h></tt> for compatibility. It
might be removed in a future version.
<aname="12"></a><p> The definitions of <ahref="tqglayoutiterator.html">TQGLayoutIterator</a>, <ahref="tqlayout.html">TQLayout</a>, <ahref="tqlayoutitem.html">TQLayoutItem</a>, <ahref="tqlayoutiterator.html">TQLayoutIterator</a>, <ahref="tqspaceritem.html">TQSpacerItem</a> and <ahref="tqwidgetitem.html">TQWidgetItem</a> have been moved from <tt><tqabstractlayout.h></tt> to <tt><tqlayout.h></tt>. The header <tt><tqabstractlayout.h></tt> has been removed.
@ -81,7 +81,7 @@ disable mouse and keyboard events for a widget.
<p> The event handlers <ahref="tqwidget.html#mousePressEvent">TQWidget::mousePressEvent</a>(),
<ahref="tqwidget.html#mouseReleaseEvent">TQWidget::mouseReleaseEvent</a>(), <ahref="tqwidget.html#mouseDoubleClickEvent">TQWidget::mouseDoubleClickEvent</a>() and
<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><p>See also <ahref="tqwidget.html#mouseTracking-prop">TQWidget::mouseTracking</a>, <ahref="tqwidget.html#grabMouse">TQWidget::grabMouse</a>(), <ahref="tqcursor.html#pos">TQCursor::pos</a>(), and <ahref="events.html">Event Classes</a>.
@ -95,7 +95,7 @@ disable mouse and keyboard events for a widget.
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
<p> The <ahref="#globalPos">globalPos</a>() is initialized to <ahref="tqcursor.html#pos">TQCursor::pos</a>(), which may not be
appropriate. Use the other constructor to specify the global
position explicitly.
@ -136,7 +136,7 @@ events.
<p> Returns the global position of the mouse pointer <em>at the time of the event</em>. This is important on asynchronous window systems
like X11. Whenever you move your widgets around in response to
mouse events, <ahref="#globalPos">globalPos</a>() may differ a lot from the current
pointer position <ahref="ntqcursor.html#pos">TQCursor::pos</a>(), and from <ahref="tqwidget.html#mapToGlobal">TQWidget::mapToGlobal</a>(
pointer position <ahref="tqcursor.html#pos">TQCursor::pos</a>(), and from <ahref="tqwidget.html#mapToGlobal">TQWidget::mapToGlobal</a>(
<ahref="#pos">pos</a>() ).
<p><p>See also <ahref="#globalX">globalX</a>() and <ahref="#globalY">globalY</a>().
<trbgcolor=#f0f0f0><td><b><ahref="tqbrush.html">TQBrush</a></b><td>Defines the fill pattern of shapes drawn by a TQPainter
<trbgcolor=#f0f0f0><td><b><ahref="tqcstring.html">TQCString</a></b><td>Abstraction of the classic C zero-terminated char array (char *)
<trbgcolor=#f0f0f0><td><b><ahref="ntqcursor.html">TQCursor</a></b><td>Mouse cursor with an arbitrary shape
<trbgcolor=#f0f0f0><td><b><ahref="tqcursor.html">TQCursor</a></b><td>Mouse cursor with an arbitrary shape
<trbgcolor=#f0f0f0><td><b><ahref="tqdeepcopy.html">TQDeepCopy</a></b><td>Template class which ensures that implicitly shared and explicitly shared classes reference unique data
<trbgcolor=#f0f0f0><td><b><ahref="tqfont.html">TQFont</a></b><td>Font used for drawing text
<trbgcolor=#f0f0f0><td><b><ahref="tqfontinfo.html">TQFontInfo</a></b><td>General information about fonts
@ -198,7 +198,7 @@ directly, so they must post an event to the widget using
<ahref="ntqapplication.html#postEvent">TQApplication::postEvent</a>(). The event will be delivered later on by
the GUI thread.
<p> Normally, the programmer would like to include some information in the
event sent to the widget. See the documentation for <ahref="qcustomevent.html">TQCustomEvent</a> for
event sent to the widget. See the documentation for <ahref="tqcustomevent.html">TQCustomEvent</a> for
more information on user-defined events.
<p><h2> Threads and <ahref="tqobject.html">TQObject</a> subclasses
</h2>
@ -208,7 +208,7 @@ thread.
<p><oltype=1>
<p><li><em>None</em> of the TQObject based classes included in the TQt library are
<em>reentrant</em>. This includes all widgets (e.g. <ahref="tqwidget.html">TQWidget</a> and
subclasses), OS kernel classes (e.g. <ahref="tqprocess.html">TQProcess</a>, <ahref="ntqaccel.html">TQAccel</a>, <ahref="tqtimer.html">TQTimer</a>), and
subclasses), OS kernel classes (e.g. <ahref="tqprocess.html">TQProcess</a>, <ahref="tqaccel.html">TQAccel</a>, <ahref="tqtimer.html">TQTimer</a>), and
all networking classes (e.g. <ahref="tqsocket.html">TQSocket</a>, <ahref="tqdns.html">TQDns</a>).
<p><li> TQObject and all of its subclasses are <em>not</em><em>thread-safe</em>. This
includes the entire event delivery system. It is important to
@ -297,7 +297,7 @@ Consult the manual of your database client for more information.
<p><ul>
<p><li> As mentioned above, <ahref="tqobject.html">TQObject</a> based classes are neither thread-safe
nor reentrant. This includes all widgets (e.g. <ahref="tqwidget.html">TQWidget</a> and
subclasses), OS kernel classes (e.g. <ahref="tqprocess.html">TQProcess</a>, <ahref="ntqaccel.html">TQAccel</a>), and all
subclasses), OS kernel classes (e.g. <ahref="tqprocess.html">TQProcess</a>, <ahref="tqaccel.html">TQAccel</a>), and all
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQAccel</h1>
<p>This is the complete list of member functions for
<ahref="ntqaccel.html">TQAccel</a>, including inherited members.
<ahref="tqaccel.html">TQAccel</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 TQAccessible</h1>
<p>This is the complete list of member functions for
<ahref="ntqaccessible.html">TQAccessible</a>, including inherited members.
<ahref="tqaccessible.html">TQAccessible</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 TQAccessibleInterface</h1>
<p>This is the complete list of member functions for
<ahref="qaccessibleinterface.html">TQAccessibleInterface</a>, including inherited members.
<ahref="tqaccessibleinterface.html">TQAccessibleInterface</a>, including inherited members.
<p> This function traverses to another object, or to a sub-element of
@ -113,7 +113,7 @@ object itself, or an ID of one of the object's sub-elements.
<p> The function returns the ID of the sub-element located in the <em>direction</em> specified. If there is nothing in the navigated <em>direction</em>, this function returns -1.
<p> Sets the text property <em>t</em> of the child object <em>control</em> to <em>text</em>. If <em>control</em> is 0, the text property of the object itself
<p> Returns a string property <em>t</em> of the child object specified by <em>control</em>, or the string property of the object itself if <em>control</em>
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQAccessibleObject</h1>
<p>This is the complete list of member functions for
<ahref="qaccessibleobject.html">TQAccessibleObject</a>, including inherited members.
<ahref="tqaccessibleobject.html">TQAccessibleObject</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 TQAssistantClient</h1>
<p>This is the complete list of member functions for
<ahref="ntqassistantclient.html">TQAssistantClient</a>, including inherited members.
<ahref="tqassistantclient.html">TQAssistantClient</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 TQAsyncIO</h1>
<p>This is the complete list of member functions for
<ahref="ntqasyncio.html">TQAsyncIO</a>, including inherited members.
<ahref="tqasyncio.html">TQAsyncIO</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 TQCDEStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqcdestyle.html">TQCDEStyle</a>, including inherited members.
<ahref="tqcdestyle.html">TQCDEStyle</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 TQChildEvent</h1>
<p>This is the complete list of member functions for
<ahref="qchildevent.html">TQChildEvent</a>, including inherited members.
<ahref="tqchildevent.html">TQChildEvent</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 TQCloseEvent</h1>
<p>This is the complete list of member functions for
<ahref="qcloseevent.html">TQCloseEvent</a>, including inherited members.
<ahref="tqcloseevent.html">TQCloseEvent</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 TQCommonStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqcommonstyle.html">TQCommonStyle</a>, including inherited members.
<ahref="tqcommonstyle.html">TQCommonStyle</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 TQContextMenuEvent</h1>
<p>This is the complete list of member functions for
<ahref="qcontextmenuevent.html">TQContextMenuEvent</a>, including inherited members.
<ahref="tqcontextmenuevent.html">TQContextMenuEvent</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 TQCursor</h1>
<p>This is the complete list of member functions for
<ahref="ntqcursor.html">TQCursor</a>, including inherited members.
<ahref="tqcursor.html">TQCursor</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 TQCustomEvent</h1>
<p>This is the complete list of member functions for
<ahref="qcustomevent.html">TQCustomEvent</a>, including inherited members.
<ahref="tqcustomevent.html">TQCustomEvent</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 TQCustomMenuItem</h1>
<p>This is the complete list of member functions for
<ahref="qcustommenuitem.html">TQCustomMenuItem</a>, including inherited members.
<ahref="tqcustommenuitem.html">TQCustomMenuItem</a>, including inherited members.
<p>Inherited by <ahref="tqcolordialog.html">TQColorDialog</a>, <ahref="ntqerrormessage.html">TQErrorMessage</a>, <ahref="tqfiledialog.html">TQFileDialog</a>, <ahref="tqfontdialog.html">TQFontDialog</a>, <ahref="ntqinputdialog.html">TQInputDialog</a>, <ahref="ntqmessagebox.html">TQMessageBox</a>, <ahref="qmotifdialog.html">TQMotifDialog</a>, <ahref="tqprogressdialog.html">TQProgressDialog</a>, <ahref="tqtabdialog.html">TQTabDialog</a>, and <ahref="tqwizard.html">TQWizard</a>.
<p>Inherited by <ahref="tqcolordialog.html">TQColorDialog</a>, <ahref="ntqerrormessage.html">TQErrorMessage</a>, <ahref="tqfiledialog.html">TQFileDialog</a>, <ahref="tqfontdialog.html">TQFontDialog</a>, <ahref="ntqinputdialog.html">TQInputDialog</a>, <ahref="ntqmessagebox.html">TQMessageBox</a>, <ahref="tqmotifdialog.html">TQMotifDialog</a>, <ahref="tqprogressdialog.html">TQProgressDialog</a>, <ahref="tqtabdialog.html">TQTabDialog</a>, and <ahref="tqwizard.html">TQWizard</a>.
<p><ahref="tqdialog-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@ -138,7 +138,7 @@ default button.
<h3> Escape Key
</h3>
<aname="1-3"></a><p> If the user presses the Esc key in a dialog, <ahref="#reject">TQDialog::reject</a>()
will be called. This will cause the window to close: the <ahref="qcloseevent.html">closeEvent</a> cannot be <ahref="qcloseevent.html#ignore">ignored</a>.
will be called. This will cause the window to close: the <ahref="tqcloseevent.html">closeEvent</a> cannot be <ahref="tqcloseevent.html#ignore">ignored</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 TQGuardedPtr</h1>
<p>This is the complete list of member functions for
<ahref="ntqguardedptr.html">TQGuardedPtr</a>, including inherited members.
<ahref="tqguardedptr.html">TQGuardedPtr</a>, including inherited members.
<p> A TQLabel is often used as a label for an interactive widget. For
this use TQLabel provides a useful mechanism for adding an
accelerator key (see <ahref="ntqaccel.html">TQAccel</a>) that will set the <ahref="focus.html#keyboard-focus">keyboard focus</a> to
accelerator key (see <ahref="tqaccel.html">TQAccel</a>) that will set the <ahref="focus.html#keyboard-focus">keyboard focus</a> to
the other widget (called the TQLabel's "buddy"). For example:
<pre>
<ahref="tqlineedit.html">TQLineEdit</a>* phoneEdit = new <ahref="tqlineedit.html">TQLineEdit</a>( this, "phoneEdit" );
@ -263,7 +263,7 @@ user presses Alt+N, and to the Phone field when the user presses
Alt+P.
<p> To unset a previously set buddy, call this function with <em>buddy</em>
set to 0.
<p><p>See also <ahref="#buddy">buddy</a>(), <ahref="#text-prop">text</a>, <ahref="ntqaccel.html">TQAccel</a>, and <ahref="#alignment-prop">alignment</a>.
<p><p>See also <ahref="#buddy">buddy</a>(), <ahref="#text-prop">text</a>, <ahref="tqaccel.html">TQAccel</a>, and <ahref="#alignment-prop">alignment</a>.
<p>Examples: <ahref="addressbook-example.html#x580">addressbook/centralwidget.cpp</a>, <ahref="tutorial2-09.html#x2642">chart/optionsform.cpp</a>, and <ahref="regexptester-example.html#x2482">regexptester/regexptester.cpp</a>.
@ -175,7 +175,7 @@ created to call <a href="ntqapplication.html#quit">TQApplication::quit</a>()
</table></center>
<p><ahref="menu-example.html">menu/menu.cpp</a> is an example of
TQMenuBar and <ahref="tqpopupmenu.html">TQPopupMenu</a> use.
<p><p>See also <ahref="tqpopupmenu.html">TQPopupMenu</a>, <ahref="ntqaccel.html">TQAccel</a>, <ahref="tqaction.html">TQAction</a>, <ahref="http://developer.apple.com/techpubs/macosx/Carbon/HumanInterfaceToolbox/Aqua/aqua.html">Aqua Style Guidelines</a>, <ahref="guibooks.html#fowler">GUI Design Handbook: Menu Bar</a>, and <ahref="application.html">Main Window and Related Classes</a>.
<p><p>See also <ahref="tqpopupmenu.html">TQPopupMenu</a>, <ahref="tqaccel.html">TQAccel</a>, <ahref="tqaction.html">TQAction</a>, <ahref="http://developer.apple.com/techpubs/macosx/Carbon/HumanInterfaceToolbox/Aqua/aqua.html">Aqua Style Guidelines</a>, <ahref="guibooks.html#fowler">GUI Design Handbook: Menu Bar</a>, and <ahref="application.html">Main Window and Related Classes</a>.
@ -254,7 +254,7 @@ The family of <a href="tqmenudata.html#insertItem">insertItem</a>() functions in
popup menu or a menu bar.
<p> A menu item is usually either a text string or a pixmap, both with
an optional icon or keyboard accelerator. For special cases it is
also possible to insert custom items (see <ahref="qcustommenuitem.html">TQCustomMenuItem</a>) or
also possible to insert custom items (see <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>) or
even widgets into popup menus.
<p> Some insertItem() members take a popup menu as an additional
argument. Use this to insert submenus into existing menus or
@ -301,7 +301,7 @@ that live in a menu bar since their accelerators will then be
installed in the menu bar itself. This also applies to stand-alone
popup menus that have a top-level widget in their <ahref="tqwidget.html#parentWidget">parentWidget</a>()
chain. The menu will then install its accelerator object on that
top-level widget. For all other cases use an independent <ahref="ntqaccel.html">TQAccel</a>
top-level widget. For all other cases use an independent <ahref="tqaccel.html">TQAccel</a>
object.
<p><b>Warning:</b> Be careful when passing a literal 0 to <ahref="tqmenudata.html#insertItem">insertItem</a>()
because some C++ compilers choose the wrong overloaded function.
@ -312,7 +312,7 @@ about signals or slots. Instead insert the items into a popup menu and
insert the popup menu into the menubar. This may be fixed in a future TQt
version.
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p>Examples: <ahref="addressbook-example.html#x569">addressbook/mainwindow.cpp</a>, <ahref="canvas-example.html#x2936">canvas/canvas.cpp</a>, <ahref="menu-example.html#x1869">menu/menu.cpp</a>, <ahref="qwerty-example.html#x371">qwerty/qwerty.cpp</a>, <ahref="scrollview-example.html#x634">scrollview/scrollview.cpp</a>, <ahref="showimg-example.html#x1327">showimg/showimg.cpp</a>, and <ahref="sound-example.html#x2810">sound/sound.cpp</a>.
@ -323,7 +323,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
menu item is connected it to the <em>receiver</em>'s <em>member</em> slot. The
icon will be displayed to the left of the text in the item.
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
@ -347,7 +347,7 @@ the item. The item is connected to the <em>member</em> slot in the <em>receiver<
<p> To look best when being highlighted as a menu item, the pixmap
should provide a mask (see <ahref="tqpixmap.html#mask">TQPixmap::mask</a>()).
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
<p> Inserts a custom menu item <em>custom</em> with an <em>icon</em> and with
@ -472,9 +472,9 @@ optional id <em>id</em>, and optional <em>index</em> position.
bars. Ownership of <em>custom</em> is transferred to the popup menu.
<p> If you want to connect a custom item to a slot, use <ahref="tqmenudata.html#connectItem">connectItem</a>().
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="qcustommenuitem.html">TQCustomMenuItem</a>.
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>.
bars. Ownership of <em>custom</em> is transferred to the popup menu.
<p> If you want to connect a custom item to a slot, use <ahref="tqmenudata.html#connectItem">connectItem</a>().
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="qcustommenuitem.html">TQCustomMenuItem</a>.
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>.
@ -129,7 +129,7 @@ They can be hidden (and shown again) with <a href="#setItemVisible">setItemVisib
<p> Menu items are stored in a list. Use <ahref="#findItem">findItem</a>() to find an item by
its list position or by its menu identifier. (See also <ahref="#indexOf">indexOf</a>()
and <ahref="#idAt">idAt</a>().)
<p><p>See also <ahref="ntqaccel.html">TQAccel</a>, <ahref="tqpopupmenu.html">TQPopupMenu</a>, <ahref="tqaction.html">TQAction</a>, and <ahref="misc.html">Miscellaneous Classes</a>.
<p><p>See also <ahref="tqaccel.html">TQAccel</a>, <ahref="tqpopupmenu.html">TQPopupMenu</a>, <ahref="tqaction.html">TQAction</a>, and <ahref="misc.html">Miscellaneous Classes</a>.
@ -278,7 +278,7 @@ The family of <a href="#insertItem">insertItem</a>() functions inserts menu item
popup menu or a menu bar.
<p> A menu item is usually either a text string or a pixmap, both with
an optional icon or keyboard accelerator. For special cases it is
also possible to insert custom items (see <ahref="qcustommenuitem.html">TQCustomMenuItem</a>) or
also possible to insert custom items (see <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>) or
even widgets into popup menus.
<p> Some insertItem() members take a popup menu as an additional
argument. Use this to insert submenus into existing menus or
@ -325,7 +325,7 @@ that live in a menu bar since their accelerators will then be
installed in the menu bar itself. This also applies to stand-alone
popup menus that have a top-level widget in their parentWidget()
chain. The menu will then install its accelerator object on that
top-level widget. For all other cases use an independent <ahref="ntqaccel.html">TQAccel</a>
top-level widget. For all other cases use an independent <ahref="tqaccel.html">TQAccel</a>
object.
<p><b>Warning:</b> Be careful when passing a literal 0 to <ahref="#insertItem">insertItem</a>()
because some C++ compilers choose the wrong overloaded function.
@ -336,7 +336,7 @@ about signals or slots. Instead insert the items into a popup menu and
insert the popup menu into the menubar. This may be fixed in a future TQt
version.
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="#removeItem">removeItem</a>(), <ahref="#changeItem">changeItem</a>(), <ahref="#setAccel">setAccel</a>(), <ahref="#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="#removeItem">removeItem</a>(), <ahref="#changeItem">changeItem</a>(), <ahref="#setAccel">setAccel</a>(), <ahref="#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p>Examples: <ahref="addressbook-example.html#x569">addressbook/mainwindow.cpp</a>, <ahref="canvas-example.html#x2936">canvas/canvas.cpp</a>, <ahref="menu-example.html#x1869">menu/menu.cpp</a>, <ahref="qwerty-example.html#x371">qwerty/qwerty.cpp</a>, <ahref="scrollview-example.html#x634">scrollview/scrollview.cpp</a>, <ahref="showimg-example.html#x1327">showimg/showimg.cpp</a>, and <ahref="sound-example.html#x2810">sound/sound.cpp</a>.
@ -347,7 +347,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
menu item is connected it to the <em>receiver</em>'s <em>member</em> slot. The
icon will be displayed to the left of the text in the item.
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="#removeItem">removeItem</a>(), <ahref="#changeItem">changeItem</a>(), <ahref="#setAccel">setAccel</a>(), <ahref="#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="#removeItem">removeItem</a>(), <ahref="#changeItem">changeItem</a>(), <ahref="#setAccel">setAccel</a>(), <ahref="#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
@ -371,7 +371,7 @@ the item. The item is connected to the <em>member</em> slot in the <em>receiver<
<p> To look best when being highlighted as a menu item, the pixmap
should provide a mask (see <ahref="tqpixmap.html#mask">TQPixmap::mask</a>()).
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="#removeItem">removeItem</a>(), <ahref="#changeItem">changeItem</a>(), <ahref="#setAccel">setAccel</a>(), <ahref="#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="#removeItem">removeItem</a>(), <ahref="#changeItem">changeItem</a>(), <ahref="#setAccel">setAccel</a>(), <ahref="#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
<p> Inserts a custom menu item <em>custom</em> with an <em>icon</em> and with
@ -496,9 +496,9 @@ optional id <em>id</em>, and optional <em>index</em> position.
bars. Ownership of <em>custom</em> is transferred to the popup menu.
<p> If you want to connect a custom item to a slot, use <ahref="#connectItem">connectItem</a>().
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="#connectItem">connectItem</a>(), <ahref="#removeItem">removeItem</a>(), and <ahref="qcustommenuitem.html">TQCustomMenuItem</a>.
<p><p>See also <ahref="#connectItem">connectItem</a>(), <ahref="#removeItem">removeItem</a>(), and <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>.
bars. Ownership of <em>custom</em> is transferred to the popup menu.
<p> If you want to connect a custom item to a slot, use <ahref="#connectItem">connectItem</a>().
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="#connectItem">connectItem</a>(), <ahref="#removeItem">removeItem</a>(), and <ahref="qcustommenuitem.html">TQCustomMenuItem</a>.
<p><p>See also <ahref="#connectItem">connectItem</a>(), <ahref="#removeItem">removeItem</a>(), and <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>.
@ -610,7 +610,7 @@ that live in a menu bar since their accelerators will then be
installed in the menu bar itself. This also applies to stand-alone
popup menus that have a top-level widget in their parentWidget()
chain. The menu will then install its accelerator object on that
top-level widget. For all other cases use an independent <ahref="ntqaccel.html">TQAccel</a>
top-level widget. For all other cases use an independent <ahref="tqaccel.html">TQAccel</a>
object.
<p> Example:
<pre>
@ -631,7 +631,7 @@ object.
<p> You can also specify the accelerator in the <ahref="#insertItem">insertItem</a>() function.
You may prefer to use <ahref="tqaction.html">TQAction</a> to associate accelerators with menu
items.
<p><p>See also <ahref="#accel">accel</a>(), <ahref="#insertItem">insertItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="tqaction.html">TQAction</a>.
<p><p>See also <ahref="#accel">accel</a>(), <ahref="#insertItem">insertItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="tqaction.html">TQAction</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 TQMotif</h1>
<p>This is the complete list of member functions for
<ahref="qmotif.html">TQMotif</a>, including inherited members.
<ahref="tqmotif.html">TQMotif</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 TQMotifDialog</h1>
<p>This is the complete list of member functions for
<ahref="qmotifdialog.html">TQMotifDialog</a>, including inherited members.
<ahref="tqmotifdialog.html">TQMotifDialog</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 TQMotifPlusStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqmotifplusstyle.html">TQMotifPlusStyle</a>, including inherited members.
<ahref="tqmotifplusstyle.html">TQMotifPlusStyle</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 TQMotifStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqmotifstyle.html">TQMotifStyle</a>, including inherited members.
<ahref="tqmotifstyle.html">TQMotifStyle</a>, including inherited members.
<p>Inherited by <ahref="ntqcdestyle.html">TQCDEStyle</a>, <ahref="ntqmotifplusstyle.html">TQMotifPlusStyle</a>, and <ahref="ntqsgistyle.html">TQSGIStyle</a>.
<p><ahref="qmotifstyle-members.html">List of all member functions.</a>
<p>Inherited by <ahref="tqcdestyle.html">TQCDEStyle</a>, <ahref="tqmotifplusstyle.html">TQMotifPlusStyle</a>, and <ahref="tqsgistyle.html">TQSGIStyle</a>.
<p><ahref="tqmotifstyle-members.html">List of all member functions.</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 TQMotifWidget</h1>
<p>This is the complete list of member functions for
<ahref="qmotifwidget.html">TQMotifWidget</a>, including inherited members.
<ahref="tqmotifwidget.html">TQMotifWidget</a>, including inherited members.
@ -543,7 +543,7 @@ sure to return TRUE. Otherwise, TQt will forward the event to the
deleted object and the program might crash.
<p><p>See also <ahref="#installEventFilter">installEventFilter</a>().
<p>Reimplemented in <ahref="ntqaccel.html#eventFilter">TQAccel</a>, <ahref="tqscrollview.html#eventFilter">TQScrollView</a>, and <ahref="tqspinbox.html#eventFilter">TQSpinBox</a>.
<p>Reimplemented in <ahref="tqaccel.html#eventFilter">TQAccel</a>, <ahref="tqscrollview.html#eventFilter">TQScrollView</a>, and <ahref="tqspinbox.html#eventFilter">TQSpinBox</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 TQPlatinumStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqplatinumstyle.html">TQPlatinumStyle</a>, including inherited members.
<ahref="tqplatinumstyle.html">TQPlatinumStyle</a>, including inherited members.
@ -130,7 +130,7 @@ synchronously with <a href="#exec">exec</a>().
<p> Technically, a popup menu consists of a list of menu items. You
add items with <ahref="tqmenudata.html#insertItem">insertItem</a>(). An item is either a string, a pixmap
or a custom item that provides its own drawing function (see
<ahref="qcustommenuitem.html">TQCustomMenuItem</a>). In addition, items can have an optional icon
<ahref="tqcustommenuitem.html">TQCustomMenuItem</a>). In addition, items can have an optional icon
drawn on the very left side and an accelerator key such as
"Ctrl+X".
<p> There are three kinds of menu items: separators, menu items that
@ -213,7 +213,7 @@ You can connect it to any slot that sets up the menu contents
Returns the accelerator key that has been defined for the menu
item <em>id</em>, or 0 if it has no accelerator key or if there is no
such menu item.
<p><p>See also <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
@ -380,7 +380,7 @@ The family of <a href="tqmenudata.html#insertItem">insertItem</a>() functions in
popup menu or a menu bar.
<p> A menu item is usually either a text string or a pixmap, both with
an optional icon or keyboard accelerator. For special cases it is
also possible to insert custom items (see <ahref="qcustommenuitem.html">TQCustomMenuItem</a>) or
also possible to insert custom items (see <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>) or
even widgets into popup menus.
<p> Some insertItem() members take a popup menu as an additional
argument. Use this to insert submenus into existing menus or
@ -427,7 +427,7 @@ that live in a menu bar since their accelerators will then be
installed in the menu bar itself. This also applies to stand-alone
popup menus that have a top-level widget in their <ahref="tqwidget.html#parentWidget">parentWidget</a>()
chain. The menu will then install its accelerator object on that
top-level widget. For all other cases use an independent <ahref="ntqaccel.html">TQAccel</a>
top-level widget. For all other cases use an independent <ahref="tqaccel.html">TQAccel</a>
object.
<p><b>Warning:</b> Be careful when passing a literal 0 to <ahref="tqmenudata.html#insertItem">insertItem</a>()
because some C++ compilers choose the wrong overloaded function.
@ -438,7 +438,7 @@ about signals or slots. Instead insert the items into a popup menu and
insert the popup menu into the menubar. This may be fixed in a future TQt
version.
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p>Examples: <ahref="addressbook-example.html#x569">addressbook/mainwindow.cpp</a>, <ahref="canvas-example.html#x2936">canvas/canvas.cpp</a>, <ahref="menu-example.html#x1869">menu/menu.cpp</a>, <ahref="qwerty-example.html#x371">qwerty/qwerty.cpp</a>, <ahref="scrollview-example.html#x634">scrollview/scrollview.cpp</a>, <ahref="showimg-example.html#x1327">showimg/showimg.cpp</a>, and <ahref="sound-example.html#x2810">sound/sound.cpp</a>.
@ -449,7 +449,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
menu item is connected it to the <em>receiver</em>'s <em>member</em> slot. The
icon will be displayed to the left of the text in the item.
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
@ -473,7 +473,7 @@ the item. The item is connected to the <em>member</em> slot in the <em>receiver<
<p> To look best when being highlighted as a menu item, the pixmap
should provide a mask (see <ahref="tqpixmap.html#mask">TQPixmap::mask</a>()).
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
<p><p>See also <ahref="tqmenudata.html#removeItem">removeItem</a>(), <ahref="tqmenudata.html#changeItem">changeItem</a>(), <ahref="tqmenudata.html#setAccel">setAccel</a>(), <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="qnamespace-h.html">ntqnamespace.h</a>.
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
<p> Inserts a custom menu item <em>custom</em> with an <em>icon</em> and with
@ -598,9 +598,9 @@ optional id <em>id</em>, and optional <em>index</em> position.
bars. Ownership of <em>custom</em> is transferred to the popup menu.
<p> If you want to connect a custom item to a slot, use <ahref="tqmenudata.html#connectItem">connectItem</a>().
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="qcustommenuitem.html">TQCustomMenuItem</a>.
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>.
bars. Ownership of <em>custom</em> is transferred to the popup menu.
<p> If you want to connect a custom item to a slot, use <ahref="tqmenudata.html#connectItem">connectItem</a>().
<p> Returns the allocated <ahref="tqmenudata.html#menu-identifier">menu identifier</a> number (<em>id</em> if <em>id</em> >= 0).
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="qcustommenuitem.html">TQCustomMenuItem</a>.
<p><p>See also <ahref="tqmenudata.html#connectItem">connectItem</a>(), <ahref="tqmenudata.html#removeItem">removeItem</a>(), and <ahref="tqcustommenuitem.html">TQCustomMenuItem</a>.
@ -726,7 +726,7 @@ that live in a menu bar since their accelerators will then be
installed in the menu bar itself. This also applies to stand-alone
popup menus that have a top-level widget in their <ahref="tqwidget.html#parentWidget">parentWidget</a>()
chain. The menu will then install its accelerator object on that
top-level widget. For all other cases use an independent <ahref="ntqaccel.html">TQAccel</a>
top-level widget. For all other cases use an independent <ahref="tqaccel.html">TQAccel</a>
object.
<p> Example:
<pre>
@ -747,7 +747,7 @@ object.
<p> You can also specify the accelerator in the <ahref="tqmenudata.html#insertItem">insertItem</a>() function.
You may prefer to use <ahref="tqaction.html">TQAction</a> to associate accelerators with menu
items.
<p><p>See also <ahref="tqmenudata.html#accel">accel</a>(), <ahref="tqmenudata.html#insertItem">insertItem</a>(), <ahref="ntqaccel.html">TQAccel</a>, and <ahref="tqaction.html">TQAction</a>.
<p><p>See also <ahref="tqmenudata.html#accel">accel</a>(), <ahref="tqmenudata.html#insertItem">insertItem</a>(), <ahref="tqaccel.html">TQAccel</a>, and <ahref="tqaction.html">TQAction</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 TQSGIStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqsgistyle.html">TQSGIStyle</a>, including inherited members.
<ahref="tqsgistyle.html">TQSGIStyle</a>, including inherited members.
<p><ahref="tqwidget-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@ -835,7 +835,7 @@ general you do not need to call it.
<p> Closes this widget. Returns TRUE if the widget was closed;
otherwise returns FALSE.
<p> First it sends the widget a <ahref="qcloseevent.html">TQCloseEvent</a>. The widget is <ahref="#hide">hidden</a> if it <ahref="qcloseevent.html#accept">accepts</a> the close event. The default implementation of
<p> First it sends the widget a <ahref="tqcloseevent.html">TQCloseEvent</a>. The widget is <ahref="#hide">hidden</a> if it <ahref="tqcloseevent.html#accept">accepts</a> the close event. The default implementation of
<ahref="#closeEvent">TQWidget::closeEvent</a>() accepts the close event.
<p> The <ahref="ntqapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>() signal is emitted when the
last visible top level widget is closed.
@ -848,21 +848,21 @@ This is an overloaded member function, provided for convenience. It behaves esse
otherwise returns FALSE.
<p> If <em>alsoDelete</em> is TRUE or the widget has the <ahref="ntqt.html#WidgetFlags-enum">WDestructiveClose</a> widget flag, the widget is also deleted. The
widget can prevent itself from being closed by rejecting the
<ahref="qcloseevent.html">TQCloseEvent</a> it gets. A close events is delivered to the widget
<ahref="tqcloseevent.html">TQCloseEvent</a> it gets. A close events is delivered to the widget
no matter if the widget is visible or not.
<p> The <ahref="ntqapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>() signal is emitted when the
last visible top level widget is closed.
<p> Note that closing the <ahref="ntqapplication.html#mainWidget">TQApplication::mainWidget</a>() terminates the
application.
<p><p>See also <ahref="#closeEvent">closeEvent</a>(), <ahref="qcloseevent.html">TQCloseEvent</a>, <ahref="#hide">hide</a>(), <ahref="ntqapplication.html#quit">TQApplication::quit</a>(), <ahref="ntqapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), and <ahref="ntqapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>().
<p><p>See also <ahref="#closeEvent">closeEvent</a>(), <ahref="tqcloseevent.html">TQCloseEvent</a>, <ahref="#hide">hide</a>(), <ahref="ntqapplication.html#quit">TQApplication::quit</a>(), <ahref="ntqapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), and <ahref="ntqapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>().
<p><p>See also <ahref="#releaseMouse">releaseMouse</a>(), <ahref="#grabKeyboard">grabKeyboard</a>(), <ahref="#releaseKeyboard">releaseKeyboard</a>(), <ahref="#grabKeyboard">grabKeyboard</a>(), and <ahref="#focusWidget">focusWidget</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 TQWindowsStyle</h1>
<p>This is the complete list of member functions for
<ahref="ntqwindowsstyle.html">TQWindowsStyle</a>, including inherited members.
<ahref="tqwindowsstyle.html">TQWindowsStyle</a>, including inherited members.
@ -218,7 +218,7 @@ makefile and build the application.)
<aname="3"></a><p> Make the size of the cannon barrel be dependent on the force.
<p> Put the cannon in the bottom-right corner.
<p> Try adding a better keyboard interface. For example, make + and -
increase and decrease the force and enter shoot. Hint: <ahref="ntqaccel.html">TQAccel</a> and
increase and decrease the force and enter shoot. Hint: <ahref="tqaccel.html">TQAccel</a> and
new addStep() and subtractStep() slots in LCDRange, like <ahref="tqslider.html#addStep">TQSlider::addStep</a>(). If you're bothered by the way the left and right
keys work (I am!), change that too.
<p> You're now ready for <ahref="tutorial1-11.html">Chapter 11.</a>
The QAccel class handles keyboard accelerator and shortcut keys.
The TQAccel class handles keyboard accelerator and shortcut keys.
.PP
A keyboard accelerator triggers an action when a certain key combination is pressed. The accelerator handles all keyboard activity for all the children of one top-level widget, so it is not affected by the keyboard focus.
.PP
@ -114,7 +114,7 @@ In most cases, you will not need to use this class directly. Use the TQAction cl
.br
.fi
.PP
A QAccel contains a list of accelerator items that can be manipulated using insertItem(), removeItem(), clear(), key() and findKey().
A TQAccel contains a list of accelerator items that can be manipulated using insertItem(), removeItem(), clear(), key() and findKey().
.PP
Each accelerator item consists of an identifier and a QKeySequence. A single key sequence consists of a keyboard code combined with modifiers (SHIFT, CTRL, ALT or UNICODE_ACCEL). For example, \fCCTRL + Key_P\fR could be a shortcut for printing a document. The key codes are listed in ntqnamespace.h. As an alternative, use UNICODE_ACCEL with the unicode code point of the character. For example, \fCUNICODE_ACCEL + 'A'\fR gives the same accelerator as Key_A.
.PP
@ -122,7 +122,7 @@ When an accelerator key is pressed, the accelerator sends out the signal activat
.PP
The activated() signal is \fInot\fR emitted when two or more accelerators match the same key. Instead, the first matching accelerator sends out the activatedAmbiguously() signal. By pressing the key multiple times, users can navigate between all matching accelerators. Some standard controls like TQPushButton and TQCheckBox connect the activatedAmbiguously() signal to the harmless setFocus() slot, whereas activated() is connected to a slot invoking the button's action. Most controls, like TQLabel and TQTabBar, treat activated() and activatedAmbiguously() as equivalent.
.PP
Use setEnabled() to enable or disable all the items in an accelerator, or setItemEnabled() to enable or disable individual items. An item is active only when both the QAccel and the item itself are enabled.
Use setEnabled() to enable or disable all the items in an accelerator, or setItemEnabled() to enable or disable individual items. An item is active only when both the TQAccel and the item itself are enabled.
.PP
The function setWhatsThis() specifies a help text that appears when the user presses an accelerator key in What's This mode.
.PP
@ -141,7 +141,7 @@ Example:
.PP
.nf
.br
QAccel *a = new QAccel( myWindow ); // create accels for myWindow
TQAccel *a = new TQAccel( myWindow ); // create accels for myWindow
Returns the identifier of the accelerator item with the key code \fIkey\fR, or -1 if the item cannot be found.
.SH "int QAccel::insertItem ( const QKeySequence & key, int id = -1 )"
.SH "int TQAccel::insertItem ( const QKeySequence & key, int id = -1 )"
Inserts an accelerator item and returns the item's identifier.
.PP
\fIkey\fR is a key code and an optional combination of SHIFT, CTRL and ALT. \fIid\fR is the accelerator item id.
@ -208,7 +208,7 @@ If \fIid\fR is negative, then the item will be assigned a unique negative identi
.PP
.nf
.br
QAccel *a = new QAccel( myWindow ); // create accels for myWindow
TQAccel *a = new TQAccel( myWindow ); // create accels for myWindow
.br
a->insertItem( CTRL + Key_P, 200 ); // Ctrl+P, e.g. to print document
.br
@ -223,39 +223,39 @@ If \fIid\fR is negative, then the item will be assigned a unique negative identi
.fi
.PP
Example: t14/gamebrd.cpp.
.SH "bool QAccel::isEnabled () const"
.SH "bool TQAccel::isEnabled () const"
Returns TRUE if the accelerator is enabled; otherwise returns FALSE.
.PP
See also setEnabled() and isItemEnabled().
.SH "bool QAccel::isItemEnabled ( int id ) const"
.SH "bool TQAccel::isItemEnabled ( int id ) const"
Returns TRUE if the accelerator item with the identifier \fIid\fR is enabled. Returns FALSE if the item is disabled or cannot be found.
.PP
See also setItemEnabled() and isEnabled().
.SH "QKeySequence QAccel::key ( int id )"
.SH "QKeySequence TQAccel::key ( int id )"
Returns the key sequence of the accelerator item with identifier \fIid\fR, or an invalid key sequence (0) if the id cannot be found.
.SH "TQString QAccel::keyToString ( QKeySequence k )\fC [static]\fR"
.SH "TQString TQAccel::keyToString ( QKeySequence k )\fC [static]\fR"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Creates an accelerator string for the key \fIk\fR. For instance CTRL+Key_O gives "Ctrl+O". The "Ctrl" etc. are translated (using TQObject::tr()) in the "QAccel" context.
Creates an accelerator string for the key \fIk\fR. For instance CTRL+Key_O gives "Ctrl+O". The "Ctrl" etc. are translated (using TQObject::tr()) in the "TQAccel" context.
.PP
The function is superfluous. Cast the QKeySequence \fIk\fR to a TQString for the same effect.
.SH "void QAccel::removeItem ( int id )"
.SH "void TQAccel::removeItem ( int id )"
Removes the accelerator item with the identifier \fIid\fR.
.SH "void QAccel::repairEventFilter ()"
.SH "void TQAccel::repairEventFilter ()"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. serves no purpose anymore
.SH "void QAccel::setEnabled ( bool enable )"
.SH "void TQAccel::setEnabled ( bool enable )"
Enables the accelerator if \fIenable\fR is TRUE, or disables it if \fIenable\fR is FALSE.
.PP
Individual keys can also be enabled or disabled using setItemEnabled(). To work, a key must be an enabled item in an enabled QAccel.
Individual keys can also be enabled or disabled using setItemEnabled(). To work, a key must be an enabled item in an enabled TQAccel.
.PP
See also isEnabled() and setItemEnabled().
.SH "void QAccel::setItemEnabled ( int id, bool enable )"
.SH "void TQAccel::setItemEnabled ( int id, bool enable )"
Enables the accelerator item with the identifier \fIid\fR if \fIenable\fR is TRUE, and disables item \fIid\fR if \fIenable\fR is FALSE.
.PP
To work, an item must be enabled and be in an enabled QAccel.
To work, an item must be enabled and be in an enabled TQAccel.
.PP
See also isItemEnabled() and isEnabled().
.SH "void QAccel::setWhatsThis ( int id, const TQString & text )"
.SH "void TQAccel::setWhatsThis ( int id, const TQString & text )"
Sets a What's This help text for the accelerator item \fIid\fR to \fItext\fR.
.PP
The text will be shown when the application is in What's This mode and the user hits the accelerator key.
@ -263,16 +263,16 @@ The text will be shown when the application is in What's This mode and the user
To set What's This help on a menu item (with or without an accelerator key), use TQMenuData::setWhatsThis().
.PP
See also whatsThis(), TQWhatsThis::inWhatsThisMode(), TQMenuData::setWhatsThis(), and TQAction::whatsThis.
Returns the shortcut key sequence for \fIstr\fR, or an invalid key sequence (0) if \fIstr\fR has no shortcut sequence.
.PP
For example, shortcutKey("E&xit") returns ALT+Key_X, shortcutKey("&Quit") returns ALT+Key_Q and shortcutKey("Quit") returns 0. (In code that does not inherit the TQt namespace class, you must write e.g. TQt::ALT+TQt::Key_Q.)
.PP
We provide a list of common accelerators in English. At the time of writing, Microsoft and Open Group do not appear to have issued equivalent recommendations for other languages.
.SH "QKeySequence QAccel::stringToKey ( const TQString & s )\fC [static]\fR"
.SH "QKeySequence TQAccel::stringToKey ( const TQString & s )\fC [static]\fR"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Returns an accelerator code for the string \fIs\fR. For example" Ctrl+O" gives CTRL+UNICODE_ACCEL+'O'. The strings "Ctrl"," Shift", "Alt" are recognized, as well as their translated equivalents in the "QAccel" context (using TQObject::tr()). Returns 0 if \fIs\fR is not recognized.
Returns an accelerator code for the string \fIs\fR. For example" Ctrl+O" gives CTRL+UNICODE_ACCEL+'O'. The strings "Ctrl"," Shift", "Alt" are recognized, as well as their translated equivalents in the "TQAccel" context (using TQObject::tr()). Returns 0 if \fIs\fR is not recognized.
.PP
This function is typically used with tr(), so that accelerator keys can be replaced in translations:
.PP
@ -282,7 +282,7 @@ This function is typically used with tr(), so that accelerator keys can be repla
@ -44,324 +44,324 @@ Inherited by QAccessibleInterface.
.br
.in -1c
.SH DESCRIPTION
The QAccessible class provides enums and static functions relating to accessibility.
The TQAccessible class provides enums and static functions relating to accessibility.
.PP
Accessibility clients use implementations of the QAccessibleInterface to read the information an accessible object exposes, or to call functions to manipulate the accessible object.
Accessibility clients use implementations of the TQAccessibleInterface to read the information an accessible object exposes, or to call functions to manipulate the accessible object.
.PP
See the plugin documentation for more details about how to redistribute TQt plugins.
.PP
See also Miscellaneous Classes.
.SS "Member Type Documentation"
.SH "QAccessible::Event"
.SH "TQAccessible::Event"
This enum type defines event types when the state of the accessible object has changed. The event types are:
.TP
\fCQAccessible::SoundPlayed\fR
\fCTQAccessible::SoundPlayed\fR
.TP
\fCQAccessible::Alert\fR
\fCTQAccessible::Alert\fR
.TP
\fCQAccessible::ForegroundChanged\fR
\fCTQAccessible::ForegroundChanged\fR
.TP
\fCQAccessible::MenuStart\fR
\fCTQAccessible::MenuStart\fR
.TP
\fCQAccessible::MenuEnd\fR
\fCTQAccessible::MenuEnd\fR
.TP
\fCQAccessible::PopupMenuStart\fR
\fCTQAccessible::PopupMenuStart\fR
.TP
\fCQAccessible::PopupMenuEnd\fR
\fCTQAccessible::PopupMenuEnd\fR
.TP
\fCQAccessible::ContextHelpStart\fR
\fCTQAccessible::ContextHelpStart\fR
.TP
\fCQAccessible::ContextHelpEnd\fR
\fCTQAccessible::ContextHelpEnd\fR
.TP
\fCQAccessible::DragDropStart\fR
\fCTQAccessible::DragDropStart\fR
.TP
\fCQAccessible::DragDropEnd\fR
\fCTQAccessible::DragDropEnd\fR
.TP
\fCQAccessible::DialogStart\fR
\fCTQAccessible::DialogStart\fR
.TP
\fCQAccessible::DialogEnd\fR
\fCTQAccessible::DialogEnd\fR
.TP
\fCQAccessible::ScrollingStart\fR
\fCTQAccessible::ScrollingStart\fR
.TP
\fCQAccessible::ScrollingEnd\fR
\fCTQAccessible::ScrollingEnd\fR
.TP
\fCQAccessible::ObjectCreated\fR
\fCTQAccessible::ObjectCreated\fR
.TP
\fCQAccessible::ObjectDestroyed\fR
\fCTQAccessible::ObjectDestroyed\fR
.TP
\fCQAccessible::ObjectShow\fR
\fCTQAccessible::ObjectShow\fR
.TP
\fCQAccessible::ObjectHide\fR
\fCTQAccessible::ObjectHide\fR
.TP
\fCQAccessible::ObjectReorder\fR
\fCTQAccessible::ObjectReorder\fR
.TP
\fCQAccessible::Focus\fR
\fCTQAccessible::Focus\fR
.TP
\fCQAccessible::Selection\fR
\fCTQAccessible::Selection\fR
.TP
\fCQAccessible::SelectionAdd\fR
\fCTQAccessible::SelectionAdd\fR
.TP
\fCQAccessible::SelectionRemove\fR
\fCTQAccessible::SelectionRemove\fR
.TP
\fCQAccessible::SelectionWithin\fR
\fCTQAccessible::SelectionWithin\fR
.TP
\fCQAccessible::StateChanged\fR
\fCTQAccessible::StateChanged\fR
.TP
\fCQAccessible::LocationChanged\fR
\fCTQAccessible::LocationChanged\fR
.TP
\fCQAccessible::NameChanged\fR
\fCTQAccessible::NameChanged\fR
.TP
\fCQAccessible::DescriptionChanged\fR
\fCTQAccessible::DescriptionChanged\fR
.TP
\fCQAccessible::ValueChanged\fR
\fCTQAccessible::ValueChanged\fR
.TP
\fCQAccessible::ParentChanged\fR
\fCTQAccessible::ParentChanged\fR
.TP
\fCQAccessible::HelpChanged\fR
\fCTQAccessible::HelpChanged\fR
.TP
\fCQAccessible::DefaultActionChanged\fR
\fCTQAccessible::DefaultActionChanged\fR
.TP
\fCQAccessible::AcceleratorChanged\fR
\fCTQAccessible::AcceleratorChanged\fR
.TP
\fCQAccessible::MenuCommand\fR
.SH "QAccessible::NavDirection"
\fCTQAccessible::MenuCommand\fR
.SH "TQAccessible::NavDirection"
This enum specifies which item to move to when navigating.
Sets \fIiface\fR to point to the implementation of the QAccessibleInterface for \fIobject\fR, and returns \fCQS_OK\fR if successfull, or sets \fIiface\fR to 0 and returns \fCQE_NOCOMPONENT\fR if no accessibility implementation for \fIobject\fR exists.
Sets \fIiface\fR to point to the implementation of the TQAccessibleInterface for \fIobject\fR, and returns \fCQS_OK\fR if successfull, or sets \fIiface\fR to 0 and returns \fCQE_NOCOMPONENT\fR if no accessibility implementation for \fIobject\fR exists.
.PP
The function uses the classname of \fIobject\fR to find a suitable implementation. If no implementation for the object's class is available the function tries to find an implementation for the object's parent class.
.PP
This function is called to answer an accessibility client's request for object information. You should never need to call this function yourself.
Notifies accessibility clients about a change in \fIobject\fR's accessibility information.
.PP
\fIreason\fR specifies the cause of the change, for example, ValueChange when the position of a slider has been changed. \fIcontrol\fR is the ID of the child element that has changed. When \fIcontrol\fR is 0, the object itself has changed.
@ -374,7 +374,7 @@ the parameters of the call is expensive you can use isActive() to
avoid unnecessary performance penalties if no client is listening.
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqaccessible.html
.BR http://doc.trolltech.com/tqaccessible.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
Returns the number of children that belong to this object. A child can provide accessibility information on it's own (e.g. a child widget), or be a sub-element of this accessible object.
.SH "int QAccessibleInterface::controlAt ( int x, int y ) const\fC [pure virtual]\fR"
.SH "int TQAccessibleInterface::controlAt ( int x, int y ) const\fC [pure virtual]\fR"
Returns the ID of the child that contains the screen coordinates (\fIx\fR, \fIy\fR). This function returns 0 if the point is positioned on the object itself. If the tested point is outside the boundaries of the object this function returns -1.
.PP
All visual objects provide this information.
.SH "bool QAccessibleInterface::doDefaultAction ( int control )\fC [pure virtual]\fR"
.SH "bool TQAccessibleInterface::doDefaultAction ( int control )\fC [pure virtual]\fR"
Calling this function performs the default action of the child object specified by \fIcontrol\fR, or the default action of the object itself if \fIcontrol\fR is 0.
This function traverses to another object, or to a sub-element of the current object. \fIdirection\fR specifies in which direction to navigate, and \fIstartControl\fR specifies the start point of the navigation, which is either 0 if the navigation starts at the object itself, or an ID of one of the object's sub-elements.
.PP
The function returns the ID of the sub-element located in the \fIdirection\fR specified. If there is nothing in the navigated \fIdirection\fR, this function returns -1.
Sets \fIiface\fR to point to the implementation of the QAccessibleInterface for the child specified with \fIcontrol\fR. If the child doesn't provide accessibility information on it's own, the value of \fIiface\fR is set to 0. For those elements, this object is responsible for exposing the child's properties.
Sets \fIiface\fR to point to the implementation of the TQAccessibleInterface for the child specified with \fIcontrol\fR. If the child doesn't provide accessibility information on it's own, the value of \fIiface\fR is set to 0. For those elements, this object is responsible for exposing the child's properties.
Sets \fIiface\fR to point to the implementation of the QAccessibleInterface for the parent object, or to 0 if there is no such implementation or object.
Sets \fIiface\fR to point to the implementation of the TQAccessibleInterface for the parent object, or to 0 if there is no such implementation or object.
.PP
All objects provide this information.
.PP
See also queryChild().
.SH "TQRect QAccessibleInterface::rect ( int control ) const\fC [pure virtual]\fR"
.SH "TQRect TQAccessibleInterface::rect ( int control ) const\fC [pure virtual]\fR"
Returns the location of the child specified with \fIcontrol\fR in screen coordinates. This function returns the location of the object itself if \fIcontrol\fR is 0.
.PP
All visual objects provide this information.
.SH "Role QAccessibleInterface::role ( int control ) const\fC [pure virtual]\fR"
.SH "Role TQAccessibleInterface::role ( int control ) const\fC [pure virtual]\fR"
Returns the role of the object if \fIcontrol\fR is 0, or the role of the object's sub-element with ID \fIcontrol\fR. The role of an object is usually static. All accessible objects have a role.
Returns the list of all the element IDs that are selected.
.PP
See also text(), role(), and state().
.SH "bool QAccessibleInterface::setFocus ( int control )\fC [pure virtual]\fR"
.SH "bool TQAccessibleInterface::setFocus ( int control )\fC [pure virtual]\fR"
Gives the focus to the child object specified by \fIcontrol\fR, or to the object itself if \fIcontrol\fR is 0.
.PP
Returns TRUE if the focus could be set; otherwise returns FALSE.
.SH "bool QAccessibleInterface::setSelected ( int control, bool on, bool extend )\fC [pure virtual]\fR"
.SH "bool TQAccessibleInterface::setSelected ( int control, bool on, bool extend )\fC [pure virtual]\fR"
Sets the selection of the child object with ID \fIcontrol\fR to \fIon\fR. If \fIextend\fR is TRUE, all child elements between the focused item and the specified child object have their selection set to \fIon\fR.
.PP
Returns TRUE if the selection could be set; otherwise returns FALSE.
.PP
See also setFocus() and clearSelection().
.SH "void QAccessibleInterface::setText ( Text t, int control, const TQString & text )\fC [pure virtual]\fR"
.SH "void TQAccessibleInterface::setText ( Text t, int control, const TQString & text )\fC [pure virtual]\fR"
Sets the text property \fIt\fR of the child object \fIcontrol\fR to \fItext\fR. If \fIcontrol\fR is 0, the text property of the object itself is set.
.SH "State QAccessibleInterface::state ( int control ) const\fC [pure virtual]\fR"
.SH "State TQAccessibleInterface::state ( int control ) const\fC [pure virtual]\fR"
Returns the current state of the object if \fIcontrol\fR is 0, or the state of the object's sub-element element with ID \fIcontrol\fR. All objects have a state.
.PP
See also text(), role(), and selection().
.SH "TQString QAccessibleInterface::text ( Text t, int control ) const\fC [pure virtual]\fR"
.SH "TQString TQAccessibleInterface::text ( Text t, int control ) const\fC [pure virtual]\fR"
Returns a string property \fIt\fR of the child object specified by \fIcontrol\fR, or the string property of the object itself if \fIcontrol\fR is 0.
.PP
The \fIName\fR is a string used by clients to identify, find or announce an accessible object for the user. All objects must have a name that is unique within their container.
@ -153,7 +153,7 @@ The accelerator is a keyboard shortcut that activates the default action of the
Sets the application override cursor to \fIcursor\fR.
.PP
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.
The QAssistantClient class provides a means of using TQt Assistant as an application's help tool.
The TQAssistantClient class provides a means of using TQt Assistant as an application's help tool.
.PP
Using TQt Assistant is simple: Create a QAssistantClient instance, then call showPage() as often as necessary to show your help pages. When you call showPage(), TQt Assistant will be launched if it isn't already running.
Using TQt Assistant is simple: Create a TQAssistantClient instance, then call showPage() as often as necessary to show your help pages. When you call showPage(), TQt Assistant will be launched if it isn't already running.
.PP
The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) TQt Assistant whenever required. If TQt Assistant is open, isOpen() returns TRUE.
The TQAssistantClient instance can open (openAssistant()) or close (closeAssistant()) TQt Assistant whenever required. If TQt Assistant is open, isOpen() returns TRUE.
.PP
One QAssistantClient instance interacts with one TQt Assistant instance, so every time you call openAssistant(), showPage() or closeAssistant() they are applied to the particular TQt Assistant instance associated with the QAssistantClient.
One TQAssistantClient instance interacts with one TQt Assistant instance, so every time you call openAssistant(), showPage() or closeAssistant() they are applied to the particular TQt Assistant instance associated with the TQAssistantClient.
.PP
When you call openAssistant() the assistantOpened() signal is emitted. Similarly when closeAssistant() is called, assistantClosed() is emitted. In either case, if an error occurs, error() is emitted.
.PP
This class is not included in the TQt library itself. To use it you must link against \fClibtqassistantclient.a\fR (Unix) or \fCqassistantclient.lib\fR (Windows), which is built into \fCINSTALL/lib\fR if you built the TQt tools (\fCINSTALL\fR is the directory where TQt is installed). If you use qmake, then you can simply add the following line to your pro file:
This class is not included in the TQt library itself. To use it you must link against \fClibtqassistantclient.a\fR (Unix) or \fCtqassistantclient.lib\fR (Windows), which is built into \fCINSTALL/lib\fR if you built the TQt tools (\fCINSTALL\fR is the directory where TQt is installed). If you use qmake, then you can simply add the following line to your pro file:
.PP
.nf
.br
@ -79,31 +79,31 @@ This class is not included in the TQt library itself. To use it you must link ag
.PP
See also "Adding Documentation to TQt Assistant" in the TQt Assistant manual.
Constructs an assistant client object. The \fIpath\fR specifies the path to the TQt Assistant executable. If \fIpath\fR is an empty string the system path (\fC%PATH%\fR or \fC$PATH\fR) is used.
.PP
The assistant client object is a child of \fIparent\fR and is called \fIname\fR.
.SH "QAssistantClient::~QAssistantClient ()"
.SH "TQAssistantClient::~TQAssistantClient ()"
Destroys the assistant client object and frees up all allocated resources.
This signal is emitted when the connection to TQt Assistant is closed. This happens when the user exits TQt Assistant, or when an error in the server or client occurs, or if closeAssistant() is called.
This signal is emitted if TQt Assistant cannot be started or if an error occurs during the initialization of the connection between TQt Assistant and the calling application. The \fImsg\fR provides an explanation of the error.
.SH "bool QAssistantClient::isOpen () const"
.SH "bool TQAssistantClient::isOpen () const"
Returns TRUE if TQt Assistant is open; otherwise returns FALSE. See the "open" property for details.
This function opens TQt Assistant and sets up the client-server communiction between the application and TQt Assistant. If it is already open, this function does nothing. If an error occurs, error() is emitted.
Call this function to make TQt Assistant show a particular \fIpage\fR. The \fIpage\fR is a filename (e.g. \fCmyhelpfile.html\fR). See "Adding Documentation to TQt Assistant" in the TQt Assistant manual for further information.
.PP
If TQt Assistant hasn't been opened yet, this function will do nothing. You can use isOpen() to determine whether TQt Assistant is up and running, or you can connect to the asssistantOpened() signal.
@ -118,7 +118,7 @@ This property holds whether TQt Assistant is open.
The TQBitmap class provides monochrome (1-bit depth) pixmaps.
.PP
The TQBitmap class is a monochrome off-screen paint device used mainly for creating custom QCursor and TQBrush objects, in TQPixmap::setMask() and for TQRegion.
The TQBitmap class is a monochrome off-screen paint device used mainly for creating custom TQCursor and TQBrush objects, in TQPixmap::setMask() and for TQRegion.
.PP
A TQBitmap is a TQPixmap with a depth of 1. If a pixmap with a depth greater than 1 is assigned to a bitmap, the bitmap will be dithered automatically. A TQBitmap is guaranteed to always have the depth 1, unless it is TQPixmap::isNull() which has depth 0.
The TQCDEStyle class provides a CDE look and feel.
.PP
This style provides a slightly improved Motif look similar to some versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright text/foreground color, the style looks quite attractive (at least for Motif fans).
.PP
Note that the functions provided by QCDEStyle are reimplementations of TQStyle functions; see TQStyle for their documentation.
Note that the functions provided by TQCDEStyle are reimplementations of TQStyle functions; see TQStyle for their documentation.
If \fIuseHighlightCols\fR is FALSE (the default), then the style will polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color.
.SH "QCDEStyle::~QCDEStyle ()\fC [virtual]\fR"
.SH "TQCDEStyle::~TQCDEStyle ()\fC [virtual]\fR"
Destroys the style.
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqcdestyle.html
.BR http://doc.trolltech.com/tqcdestyle.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,7 +7,7 @@
.ad l
.nh
.SH NAME
QCloseEvent \- Parameters that describe a close event
TQCloseEvent \- Parameters that describe a close event
.SH SYNOPSIS
\fC#include <tqevent.h>\fR
.PP
@ -16,7 +16,7 @@ Inherits TQEvent.
.SS "Public Members"
.in +1c
.ti -1c
.BI "\fBQCloseEvent\fR ()"
.BI "\fBTQCloseEvent\fR ()"
.br
.ti -1c
.BI "bool \fBisAccepted\fR () const"
@ -29,7 +29,7 @@ Inherits TQEvent.
.br
.in -1c
.SH DESCRIPTION
The QCloseEvent class contains parameters that describe a close event.
The TQCloseEvent class contains parameters that describe a close event.
.PP
Close events are sent to widgets that the user wants to close, usually by choosing "Close" from the window menu, or by clicking the `X' titlebar button. They are also sent when you call TQWidget::close() to close a widget programmatically.
.PP
@ -51,11 +51,11 @@ The isAccepted() function returns TRUE if the event's receiver has agreed to clo
.PP
See also TQWidget::close(), TQWidget::hide(), TQObject::destroyed(), QApplication::setMainWidget(), QApplication::lastWindowClosed(), QApplication::exec(), QApplication::quit(), and Event Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QCloseEvent::QCloseEvent ()"
.SH "TQCloseEvent::TQCloseEvent ()"
Constructs a close event object with the accept parameter flag set to FALSE.
.PP
See also accept().
.SH "void QCloseEvent::accept ()"
.SH "void TQCloseEvent::accept ()"
Sets the accept flag of the close event object.
.PP
Setting the accept flag indicates that the receiver of this event agrees to close the widget.
@ -68,7 +68,7 @@ See also ignore() and TQWidget::hide().
.PP
Examples:
.)l action/application.cpp, application/application.cpp, mdi/application.cpp, popup/popup.cpp, and qwerty/qwerty.cpp.
.SH "void QCloseEvent::ignore ()"
.SH "void TQCloseEvent::ignore ()"
Clears the accept flag of the close event object.
.PP
Clearing the accept flag indicates that the receiver of this event does not want the widget to be closed.
@ -79,13 +79,13 @@ See also accept().
.PP
Examples:
.)l action/application.cpp, application/application.cpp, mdi/application.cpp, and qwerty/qwerty.cpp.
.SH "bool QCloseEvent::isAccepted () const"
.SH "bool TQCloseEvent::isAccepted () const"
Returns TRUE if the receiver of the event has agreed to close the widget; otherwise returns FALSE.
.PP
See also accept() and ignore().
.SH "SEE ALSO"
.BR http://doc.trolltech.com/qcloseevent.html
.BR http://doc.trolltech.com/tqcloseevent.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,7 +7,7 @@
.ad l
.nh
.SH NAME
QContextMenuEvent \- Parameters that describe a context menu event
TQContextMenuEvent \- Parameters that describe a context menu event
.SH SYNOPSIS
\fC#include <tqevent.h>\fR
.PP
@ -19,10 +19,10 @@ Inherits TQEvent.
.BI "enum \fBReason\fR { Mouse, Keyboard, Other }"
.br
.ti -1c
.BI "\fBQContextMenuEvent\fR ( Reason reason, const TQPoint & pos, const TQPoint & globalPos, int state )"
.BI "\fBTQContextMenuEvent\fR ( Reason reason, const TQPoint & pos, const TQPoint & globalPos, int state )"
.br
.ti -1c
.BI "\fBQContextMenuEvent\fR ( Reason reason, const TQPoint & pos, int state )"
.BI "\fBTQContextMenuEvent\fR ( Reason reason, const TQPoint & pos, int state )"
.br
.ti -1c
.BI "int \fBx\fR () const"
@ -65,7 +65,7 @@ Inherits TQEvent.
.br
.in -1c
.SH DESCRIPTION
The QContextMenuEvent class contains parameters that describe a context menu event.
The TQContextMenuEvent class contains parameters that describe a context menu event.
.PP
Context menu events are sent to widgets when a user triggers a context menu. What triggers this is platform dependent. For example, on Windows, pressing the menu button or releasing the right mouse button will cause this event to be sent.
.PP
@ -75,30 +75,30 @@ Context menu events contain a special accept flag that indicates whether the rec
.PP
See also TQPopupMenu and Event Classes.
.SS "Member Type Documentation"
.SH "QContextMenuEvent::Reason"
.SH "TQContextMenuEvent::Reason"
This enum describes the reason the ContextMenuEvent was sent. The values are:
.TP
\fCQContextMenuEvent::Mouse\fR - The mouse caused the event to be sent. Normally this means the right mouse button was clicked, but this is platform specific.
\fCTQContextMenuEvent::Mouse\fR - The mouse caused the event to be sent. Normally this means the right mouse button was clicked, but this is platform specific.
.TP
\fCQContextMenuEvent::Keyboard\fR - The keyboard caused this event to be sent. On Windows this means the menu button was pressed.
\fCTQContextMenuEvent::Keyboard\fR - The keyboard caused this event to be sent. On Windows this means the menu button was pressed.
.TP
\fCQContextMenuEvent::Other\fR - The event was sent by some other means (i.e. not by the mouse or keyboard).
\fCTQContextMenuEvent::Other\fR - The event was sent by some other means (i.e. not by the mouse or keyboard).
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QContextMenuEvent::QContextMenuEvent ( Reason reason, const TQPoint & pos, const TQPoint & globalPos, int state )"
.SH "TQContextMenuEvent::TQContextMenuEvent ( Reason reason, const TQPoint & pos, const TQPoint & globalPos, int state )"
Constructs a context menu event object with the accept parameter flag set to FALSE.
.PP
The \fIreason\fR parameter must be QContextMenuEvent::Mouse or QContextMenuEvent::Keyboard.
The \fIreason\fR parameter must be TQContextMenuEvent::Mouse or TQContextMenuEvent::Keyboard.
.PP
The \fIpos\fR parameter specifies the mouse position relative to the receiving widget. \fIglobalPos\fR is the mouse position in absolute coordinates. \fIstate\fR is the ButtonState at the time of the event.
.SH "QContextMenuEvent::QContextMenuEvent ( Reason reason, const TQPoint & pos, int state )"
.SH "TQContextMenuEvent::TQContextMenuEvent ( Reason reason, const TQPoint & pos, int state )"
Constructs a context menu event object with the accept parameter flag set to FALSE.
.PP
The \fIreason\fR parameter must be QContextMenuEvent::Mouse or QContextMenuEvent::Keyboard.
The \fIreason\fR parameter must be TQContextMenuEvent::Mouse or TQContextMenuEvent::Keyboard.
.PP
The \fIpos\fR parameter specifies the mouse position relative to the receiving widget. \fIstate\fR is the ButtonState at the time of the event.
.PP
The globalPos() is initialized to QCursor::pos(), which may not be appropriate. Use the other constructor to specify the global position explicitly.
.SH "void QContextMenuEvent::accept ()"
The globalPos() is initialized to TQCursor::pos(), which may not be appropriate. Use the other constructor to specify the global position explicitly.
.SH "void TQContextMenuEvent::accept ()"
Sets the accept flag of the context event object.
.PP
Setting the accept flag indicates that the receiver of this event has processed the event. Processing the event means you did something with it and it will be implicitly consumed.
@ -106,7 +106,7 @@ Setting the accept flag indicates that the receiver of this event has processed
The accept flag is not set by default.
.PP
See also ignore() and consume().
.SH "void QContextMenuEvent::consume ()"
.SH "void TQContextMenuEvent::consume ()"
Sets the consume flag of the context event object.
.PP
Setting the consume flag indicates that the receiver of this event does not want the event to be propagated further (i.e. not sent to parent classes.)
@ -114,19 +114,19 @@ Setting the consume flag indicates that the receiver of this event does not want
Returns the global position of the mouse pointer at the time of the event.
.PP
See also x(), y(), and pos().
.SH "int QContextMenuEvent::globalX () const"
.SH "int TQContextMenuEvent::globalX () const"
Returns the global x-position of the mouse pointer at the time of the event.
.PP
See also globalY() and globalPos().
.SH "int QContextMenuEvent::globalY () const"
.SH "int TQContextMenuEvent::globalY () const"
Returns the global y-position of the mouse pointer at the time of the event.
.PP
See also globalX() and globalPos().
.SH "void QContextMenuEvent::ignore ()"
.SH "void TQContextMenuEvent::ignore ()"
Clears the accept flag of the context event object.
.PP
Clearing the accept flag indicates that the receiver of this event does not need to show a context menu. This will implicitly remove the consumed flag as well.
@ -134,35 +134,35 @@ Clearing the accept flag indicates that the receiver of this event does not need
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
The returned value is LeftButton, RightButton, MidButton, ShiftButton, ControlButton and AltButton OR'ed together.
.SH "int QContextMenuEvent::x () const"
.SH "int TQContextMenuEvent::x () const"
Returns the x-position of the mouse pointer, relative to the widget that received the event.
.PP
See also y() and pos().
.SH "int QContextMenuEvent::y () const"
.SH "int TQContextMenuEvent::y () const"
Returns the y-position of the mouse pointer, relative to the widget that received the event.
The QCursor class provides a mouse cursor with an arbitrary shape.
The TQCursor class provides a mouse cursor with an arbitrary shape.
.PP
This class is mainly used to create mouse cursors that are associated with particular widgets and to get and set the position of the mouse cursor.
.PP
@ -97,11 +97,11 @@ Qt has a number of standard cursor shapes, but you can also make custom cursor s
.PP
To associate a cursor with a widget, use TQWidget::setCursor(). To associate a cursor with all widgets (normally for a short period of time), use QApplication::setOverrideCursor().
.PP
To set a cursor shape use QCursor::setShape() or use the QCursor constructor which takes the shape as argument, or you can use one of the predefined cursors defined in the CursorShape enum.
To set a cursor shape use TQCursor::setShape() or use the TQCursor constructor which takes the shape as argument, or you can use one of the predefined cursors defined in the CursorShape enum.
.PP
If you want to create a cursor with your own bitmap, either use the QCursor constructor which takes a bitmap and a mask or the constructor which takes a pixmap as arguments.
If you want to create a cursor with your own bitmap, either use the TQCursor constructor which takes a bitmap and a mask or the constructor which takes a pixmap as arguments.
.PP
To set or get the position of the mouse cursor use the static methods QCursor::pos() and QCursor::setPos().
To set or get the position of the mouse cursor use the static methods TQCursor::pos() and TQCursor::setPos().
.PP
<center>
.ce 1
@ -120,15 +120,15 @@ l - l. TQt::CursorShape Values Cursor Names TQt::ArrowCursor left_ptr TQt::UpArr
.fi
</center>
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QCursor::QCursor ()"
.SH "TQCursor::TQCursor ()"
Constructs a cursor with the default arrow shape.
.SH "QCursor::QCursor ( int shape )"
.SH "TQCursor::TQCursor ( int shape )"
Constructs a cursor with the specified \fIshape\fR.
.PP
See CursorShape for a list of shapes.
.PP
See also setShape().
.SH "QCursor::QCursor ( const TQBitmap & bitmap, const TQBitmap & mask, int hotX = -1, int hotY = -1 )"
.SH "TQCursor::TQCursor ( const TQBitmap & bitmap, const TQBitmap & mask, int hotX = -1, int hotY = -1 )"
Constructs a custom bitmap cursor.
.PP
\fIbitmap\fR and \fImask\fR make up the bitmap. \fIhotX\fR and \fIhotY\fR define the cursor's hot spot.
@ -150,7 +150,7 @@ Use the global TQt color \fCcolor0\fR to draw 0-pixels and \fCcolor1\fR to draw
Valid cursor sizes depend on the display hardware (or the underlying window system). We recommend using 32x32 cursors, because this size is supported on all platforms. Some platforms also support 16x16, 48x48 and 64x64 cursors.
.PP
See also TQBitmap::TQBitmap() and TQBitmap::setMask().
.SH "QCursor::QCursor ( const TQPixmap & pixmap, int hotX = -1, int hotY = -1 )"
.SH "TQCursor::TQCursor ( const TQPixmap & pixmap, int hotX = -1, int hotY = -1 )"
Constructs a custom pixmap cursor.
.PP
\fIpixmap\fR is the image. It is usual to give it a mask (set using TQPixmap::setMask()). \fIhotX\fR and \fIhotY\fR define the cursor's hot spot.
@ -162,35 +162,35 @@ Valid cursor sizes depend on the display hardware (or the underlying window syst
Currently, only black-and-white pixmaps can be used.
.PP
See also TQPixmap::TQPixmap() and TQPixmap::setMask().
.SH "QCursor::QCursor ( const QCursor & c )"
.SH "TQCursor::TQCursor ( const TQCursor & c )"
Constructs a copy of the cursor \fIc\fR.
.SH "QCursor::QCursor ( HCURSOR handle )"
.SH "TQCursor::TQCursor ( HCURSOR handle )"
Creates a cursor with the specified window system handle \fIhandle\fR.
.PP
\fBWarning:\fR Portable in principle, but if you use it you are probably about to do something non-portable. Be careful.
.SH "QCursor::~QCursor ()"
.SH "TQCursor::~TQCursor ()"
Destroys the cursor.
.SH "const TQBitmap * QCursor::bitmap () const"
.SH "const TQBitmap * TQCursor::bitmap () const"
Returns the cursor bitmap, or 0 if it is one of the standard cursors.
.SH "void QCursor::cleanup ()\fC [static]\fR"
.SH "void TQCursor::cleanup ()\fC [static]\fR"
Internal function that deinitializes the predefined cursors. This function is called from the QApplication destructor.
.PP
See also initialize().
.SH "HANDLE QCursor::handle () const"
.SH "HANDLE TQCursor::handle () const"
Returns the window system cursor handle.
.PP
\fBWarning:\fR Portable in principle, but if you use it you are probably about to do something non-portable. Be careful.
.SH "TQPoint QCursor::hotSpot () const"
.SH "TQPoint TQCursor::hotSpot () const"
Returns the cursor hot spot, or (0, 0) if it is one of the standard cursors.
.SH "void QCursor::initialize ()\fC [static]\fR"
.SH "void TQCursor::initialize ()\fC [static]\fR"
Internal function that initializes the predefined cursors. This function is called from the QApplication constructor.
.PP
See also cleanup().
.SH "const TQBitmap * QCursor::mask () const"
.SH "const TQBitmap * TQCursor::mask () const"
Returns the cursor bitmap mask, or 0 if it is one of the standard cursors.
.SH "QCursor & QCursor::operator= ( const QCursor & c )"
.SH "TQCursor & TQCursor::operator= ( const TQCursor & c )"
Assigns \fIc\fR to this cursor and returns a reference to this cursor.
.SH "TQPoint QCursor::pos ()\fC [static]\fR"
.SH "TQPoint TQCursor::pos ()\fC [static]\fR"
Returns the position of the cursor (hot spot) in global screen coordinates.
.PP
You can call TQWidget::mapFromGlobal() to translate it to widget coordinates.
@ -199,36 +199,36 @@ See also setPos(), TQWidget::mapFromGlobal(), and TQWidget::mapToGlobal().
.PP
Examples:
.)l chart/canvasview.cpp, fileiconview/tqfileiconview.cpp, and menu/menu.cpp.
.SH "void QCursor::setPos ( int x, int y )\fC [static]\fR"
.SH "void TQCursor::setPos ( int x, int y )\fC [static]\fR"
Moves the cursor (hot spot) to the global screen position (\fIx\fR, \fIy\fR).
.PP
You can call TQWidget::mapToGlobal() to translate widget coordinates to global screen coordinates.
.PP
See also pos(), TQWidget::mapFromGlobal(), and TQWidget::mapToGlobal().
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,7 +7,7 @@
.ad l
.nh
.SH NAME
QCustomEvent \- Support for custom events
TQCustomEvent \- Support for custom events
.SH SYNOPSIS
\fC#include <tqevent.h>\fR
.PP
@ -16,10 +16,10 @@ Inherits TQEvent.
.SS "Public Members"
.in +1c
.ti -1c
.BI "\fBQCustomEvent\fR ( int type )"
.BI "\fBTQCustomEvent\fR ( int type )"
.br
.ti -1c
.BI "\fBQCustomEvent\fR ( Type type, void * data )"
.BI "\fBTQCustomEvent\fR ( Type type, void * data )"
.br
.ti -1c
.BI "void * \fBdata\fR () const"
@ -29,21 +29,21 @@ Inherits TQEvent.
.br
.in -1c
.SH DESCRIPTION
The QCustomEvent class provides support for custom events.
The TQCustomEvent 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.
TQCustomEvent 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 TQEvent::Type enum.
TQCustomEvent 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.
TQCustomEvent 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
QCustomEvent can be used as-is for simple user-defined event types, but normally you will want to make a subclass of it for your event types. In a subclass, you can add data members that are suitable for your event type.
TQCustomEvent can be used as-is for simple user-defined event types, but normally you will want to make a subclass of it for your event types. In a subclass, you can add data members that are suitable for your event type.
.PP
Example:
.PP
.nf
.br
class ColorChangeEvent : public QCustomEvent
class ColorChangeEvent : public TQCustomEvent
.br
{
.br
@ -51,7 +51,7 @@ Example:
.br
ColorChangeEvent( TQColor color )
.br
: QCustomEvent( 65432 ), c( color ) {}
: TQCustomEvent( 65432 ), c( color ) {}
.br
TQColor color() const { return c; }
.br
@ -73,7 +73,7 @@ Example:
// To receive an event of this custom event type:
.br
.br
void MyWidget::customEvent( QCustomEvent * e )
void MyWidget::customEvent( TQCustomEvent * e )
.br
{
.br
@ -91,21 +91,21 @@ Example:
.PP
See also TQWidget::customEvent(), QApplication::notify(), and Event Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QCustomEvent::QCustomEvent ( int type )"
.SH "TQCustomEvent::TQCustomEvent ( int type )"
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 )"
.SH "TQCustomEvent::TQCustomEvent ( 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 TQEvent::Type).
.SH "void * QCustomEvent::data () const"
.SH "void * TQCustomEvent::data () const"
Returns a pointer to the generic event data.
.PP
See also setData().
.SH "void QCustomEvent::setData ( void * data )"
.SH "void TQCustomEvent::setData ( void * data )"
Sets the generic data pointer to \fIdata\fR.
.PP
See also data().
.SH "SEE ALSO"
.BR http://doc.trolltech.com/qcustomevent.html
.BR http://doc.trolltech.com/tqcustomevent.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,7 +7,7 @@
.ad l
.nh
.SH NAME
QCustomMenuItem \- Abstract base class for custom menu items in popup menus
TQCustomMenuItem \- Abstract base class for custom menu items in popup menus
.SH SYNOPSIS
\fC#include <tqmenudata.h>\fR
.PP
@ -16,10 +16,10 @@ Inherits Qt.
.SS "Public Members"
.in +1c
.ti -1c
.BI "\fBQCustomMenuItem\fR ()"
.BI "\fBTQCustomMenuItem\fR ()"
.br
.ti -1c
.BI "virtual \fB~QCustomMenuItem\fR ()"
.BI "virtual \fB~TQCustomMenuItem\fR ()"
.br
.ti -1c
.BI "virtual bool \fBfullSpan\fR () const"
@ -38,7 +38,7 @@ Inherits Qt.
.br
.in -1c
.SH DESCRIPTION
The QCustomMenuItem class is an abstract base class for custom menu items in popup menus.
The TQCustomMenuItem class is an abstract base class for custom menu items in popup menus.
.PP
A custom menu item is a menu item that is defined by two pure virtual functions, paint() and sizeHint(). The size hint tells the menu how much space it needs to reserve for this item, and paint is called whenever the item needs painting.
.PP
@ -50,38 +50,38 @@ By default, a custom item can also have an icon and a keyboard accelerator. You
.PP
If you want the custom item to be treated just as a separator, reimplement isSeparator() to return TRUE.
.PP
Note that you can insert pixmaps or bitmaps as items into a popup menu without needing to create a QCustomMenuItem. However, custom menu items offer more flexibility, and -- especially important with Windows style -- provide the possibility of drawing the item with a different color when it is highlighted.
Note that you can insert pixmaps or bitmaps as items into a popup menu without needing to create a TQCustomMenuItem. However, custom menu items offer more flexibility, and -- especially important with Windows style -- provide the possibility of drawing the item with a different color when it is highlighted.
.PP
menu/menu.cpp shows a simple example how custom menu items can be used.
.PP
Note: the current implementation of QCustomMenuItem will not recognize shortcut keys that are from text with ampersands. Normal accelerators work though.
Note: the current implementation of TQCustomMenuItem will not recognize shortcut keys that are from text with ampersands. Normal accelerators work though.
.PP
.ce 1
.B "[Image Omitted]"
.PP
See also TQMenuData, TQPopupMenu, and Miscellaneous Classes.
Returns TRUE if this item wants to span the entire popup menu width; otherwise returns FALSE. The default is FALSE, meaning that the menu may show an icon and an accelerator key for this item as well.
Returns TRUE if this item is just a separator; otherwise returns FALSE.
.SH "void QCustomMenuItem::paint ( TQPainter * p, const TQColorGroup & cg, bool act, bool enabled, int x, int y, int w, int h )\fC [pure virtual]\fR"
.SH "void TQCustomMenuItem::paint ( TQPainter * p, const TQColorGroup & cg, bool act, bool enabled, int x, int y, int w, int h )\fC [pure virtual]\fR"
Paints this item. When this function is invoked, the painter \fIp\fR is set to a font and foreground color suitable for a menu item text using color group \fIcg\fR. The item is active if \fIact\fR is TRUE and enabled if \fIenabled\fR is TRUE. The geometry values \fIx\fR, \fIy\fR, \fIw\fR and \fIh\fR specify where to draw the item.
.PP
Do not draw any background, this has already been done by the popup menu according to the current GUI style.
.SH "void QCustomMenuItem::setFont ( const TQFont & font )\fC [virtual]\fR"
.SH "void TQCustomMenuItem::setFont ( const TQFont & font )\fC [virtual]\fR"
Sets the font of the custom menu item to \fIfont\fR.
.PP
This function is called whenever the font in the popup menu changes. For menu items that show their own individual font entry, you want to ignore this.
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,35 +7,35 @@
.ad l
.nh
.SH NAME
QGuardedPtr \- Template class that provides guarded pointers to TQObjects
TQGuardedPtr \- Template class that provides guarded pointers to TQObjects
.SH SYNOPSIS
\fC#include <ntqguardedptr.h>\fR
\fC#include <tqguardedptr.h>\fR
.PP
.SS "Public Members"
.in +1c
.ti -1c
.BI "\fBQGuardedPtr\fR ()"
.BI "\fBTQGuardedPtr\fR ()"
.br
.ti -1c
.BI "\fBQGuardedPtr\fR ( T * p )"
.BI "\fBTQGuardedPtr\fR ( T * p )"
.br
.ti -1c
.BI "\fBQGuardedPtr\fR ( const QGuardedPtr<T> & p )"
.BI "\fBTQGuardedPtr\fR ( const TQGuardedPtr<T> & p )"
.br
.ti -1c
.BI "\fB~QGuardedPtr\fR ()"
.BI "\fB~TQGuardedPtr\fR ()"
.br
.ti -1c
.BI "QGuardedPtr<T> & \fBoperator=\fR ( const QGuardedPtr<T> & p )"
.BI "TQGuardedPtr<T> & \fBoperator=\fR ( const TQGuardedPtr<T> & p )"
.br
.ti -1c
.BI "QGuardedPtr<T> & \fBoperator=\fR ( T * p )"
.BI "TQGuardedPtr<T> & \fBoperator=\fR ( T * p )"
.br
.ti -1c
.BI "bool \fBoperator==\fR ( const QGuardedPtr<T> & p ) const"
.BI "bool \fBoperator==\fR ( const TQGuardedPtr<T> & p ) const"
.br
.ti -1c
.BI "bool \fBoperator!=\fR ( const QGuardedPtr<T> & p ) const"
.BI "bool \fBoperator!=\fR ( const TQGuardedPtr<T> & p ) const"
.br
.ti -1c
.BI "bool \fBisNull\fR () const"
@ -51,9 +51,9 @@ QGuardedPtr \- Template class that provides guarded pointers to TQObjects
.br
.in -1c
.SH DESCRIPTION
The QGuardedPtr class is a template class that provides guarded pointers to TQObjects.
The TQGuardedPtr class is a template class that provides guarded pointers to TQObjects.
.PP
A guarded pointer, \fCQGuardedPtr<X>\fR, behaves like a normal C++ pointer \fCX*\fR, except that it is automatically set to 0 when the referenced object is destroyed (unlike normal C++ pointers, which become "dangling pointers" in such cases). \fCX\fR must be a subclass of TQObject.
A guarded pointer, \fCTQGuardedPtr<X>\fR, behaves like a normal C++ pointer \fCX*\fR, except that it is automatically set to 0 when the referenced object is destroyed (unlike normal C++ pointers, which become "dangling pointers" in such cases). \fCX\fR must be a subclass of TQObject.
.PP
Guarded pointers are useful whenever you need to store a pointer to a TQObject that is owned by someone else and therefore might be destroyed while you still hold a reference to it. You can safely test the pointer for validity.
.PP
@ -61,7 +61,7 @@ Example:
.PP
.nf
.br
QGuardedPtr<TQLabel> label = new TQLabel( 0, "label" );
TQGuardedPtr<TQLabel> label = new TQLabel( 0, "label" );
.br
label->setText( "I like guarded pointers" );
.br
@ -81,49 +81,49 @@ Example:
.PP
The program will output \fCThe label has been destroyed\fR rather than dereferencing an invalid address in \fClabel->show()\fR.
.PP
The functions and operators available with a QGuardedPtr are the same as those available with a normal unguarded pointer, except the pointer arithmetic operators (++, --, -, and +), which are normally used only with arrays of objects. Use them like normal pointers and you will not need to read this class documentation.
The functions and operators available with a TQGuardedPtr are the same as those available with a normal unguarded pointer, except the pointer arithmetic operators (++, --, -, and +), which are normally used only with arrays of objects. Use them like normal pointers and you will not need to read this class documentation.
.PP
For creating guarded pointers, you can construct or assign to them from an X* or from another guarded pointer of the same type. You can compare them with each other using operator==() and operator!=(), or test for 0 with isNull(). And you can dereference them using either the \fC*x\fR or the \fCx->member\fR notation.
.PP
A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a QGuardedPtr<TQWidget>, you can pass it to a function that requires a TQWidget*. For this reason, it is of little value to declare functions to take a QGuardedPtr as a parameter; just use normal pointers. Use a QGuardedPtr when you are storing a pointer over time.
A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a TQGuardedPtr<TQWidget>, you can pass it to a function that requires a TQWidget*. For this reason, it is of little value to declare functions to take a TQGuardedPtr as a parameter; just use normal pointers. Use a TQGuardedPtr when you are storing a pointer over time.
.PP
Note again that class \fIX\fR must inherit TQObject, or a compilation or link error will result.
.PP
See also Object Model.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QGuardedPtr::QGuardedPtr ()"
.SH "TQGuardedPtr::TQGuardedPtr ()"
Constructs a 0 guarded pointer.
.PP
See also isNull().
.SH "QGuardedPtr::QGuardedPtr ( T * p )"
.SH "TQGuardedPtr::TQGuardedPtr ( T * p )"
Constructs a guarded pointer that points to same object as \fIp\fR points to.
.SH "QGuardedPtr::QGuardedPtr ( const QGuardedPtr<T> & p )"
.SH "TQGuardedPtr::TQGuardedPtr ( const TQGuardedPtr<T> & p )"
Copy one guarded pointer from another. The constructed guarded pointer points to the same object that \fIp\fR points to (which may be 0).
.SH "QGuardedPtr::~QGuardedPtr ()"
.SH "TQGuardedPtr::~TQGuardedPtr ()"
Destroys the guarded pointer. Just like a normal pointer, destroying a guarded pointer does \fInot\fR destroy the object being pointed to.
.SH "bool QGuardedPtr::isNull () const"
.SH "bool TQGuardedPtr::isNull () const"
Returns \fCTRUE\fR if the referenced object has been destroyed or if there is no referenced object; otherwise returns FALSE.
.SH "QGuardedPtr::operator T * () const"
Cast operator; implements pointer semantics. Because of this function you can pass a QGuardedPtr<X> to a function where an X* is required.
.SH "bool QGuardedPtr::operator!= ( const QGuardedPtr<T> & p ) const"
.SH "TQGuardedPtr::operator T * () const"
Cast operator; implements pointer semantics. Because of this function you can pass a TQGuardedPtr<X> to a function where an X* is required.
.SH "bool TQGuardedPtr::operator!= ( const TQGuardedPtr<T> & p ) const"
Inequality operator; implements pointer semantics, the negation of operator==(). Returns TRUE if \fIp\fR and this guarded pointer are not pointing to the same object; otherwise returns FALSE.
.SH "T & QGuardedPtr::operator* () const"
.SH "T & TQGuardedPtr::operator* () const"
Dereference operator; implements pointer semantics. Just use this operator as you would with a normal C++ pointer.
.SH "T * QGuardedPtr::operator-> () const"
.SH "T * TQGuardedPtr::operator-> () const"
Overloaded arrow operator; implements pointer semantics. Just use this operator as you would with a normal C++ pointer.
.SH "QGuardedPtr<T> & QGuardedPtr::operator= ( const QGuardedPtr<T> & p )"
.SH "TQGuardedPtr<T> & TQGuardedPtr::operator= ( const TQGuardedPtr<T> & p )"
Assignment operator. This guarded pointer then points to the same object as \fIp\fR points to.
.SH "QGuardedPtr<T> & QGuardedPtr::operator= ( T * p )"
.SH "TQGuardedPtr<T> & TQGuardedPtr::operator= ( T * p )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Assignment operator. This guarded pointer then points to the same object as \fIp\fR points to.
.SH "bool QGuardedPtr::operator== ( const QGuardedPtr<T> & p ) const"
.SH "bool TQGuardedPtr::operator== ( const TQGuardedPtr<T> & p ) const"
Equality operator; implements traditional pointer semantics. Returns TRUE if both \fIp\fR and this guarded pointer are 0, or if both \fIp\fR and this pointer point to the same object; otherwise returns FALSE.
.PP
See also operator!=().
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqguardedptr.html
.BR http://doc.trolltech.com/tqguardedptr.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
@ -75,14 +75,14 @@ The QKeySequence class encapsulates a key sequence as used by accelerators.
.PP
A key sequence consists of up to four keyboard codes, each optionally combined with modifiers, e.g. SHIFT, CTRL, ALT, META, or UNICODE_ACCEL. For example, \fCCTRL + Key_P\fR might be a sequence used as a shortcut for printing a document. The key codes are listed in ntqnamespace.h. As an alternative, use UNICODE_ACCEL with the unicode code point of the character. For example, \fCUNICODE_ACCEL + 'A'\fR gives the same key sequence as Key_A.
.PP
Key sequences can be constructed either from an integer key code, or from a human readable translatable string such as" Ctrl+X,Alt+Space". A key sequence can be cast to a TQString to obtain a human readable translated version of the sequence. Translations are done in the "QAccel" context.
Key sequences can be constructed either from an integer key code, or from a human readable translatable string such as" Ctrl+X,Alt+Space". A key sequence can be cast to a TQString to obtain a human readable translated version of the sequence. Translations are done in the "TQAccel" context.
Creates a key sequence from the string \fIkey\fR. For example" Ctrl+O" gives CTRL+UNICODE_ACCEL+'O'. The strings "Ctrl"," Shift", "Alt" and "Meta" are recognized, as well as their translated equivalents in the "QAccel" context (using TQObject::tr()).
Creates a key sequence from the string \fIkey\fR. For example" Ctrl+O" gives CTRL+UNICODE_ACCEL+'O'. The strings "Ctrl"," Shift", "Alt" and "Meta" are recognized, as well as their translated equivalents in the "TQAccel" context (using TQObject::tr()).
.PP
Multiple key codes (up to four) may be entered by separating them with commas, e.g. "Alt+X,Ctrl+S,Q".
.PP
@ -118,7 +118,7 @@ Returns TRUE if the key sequence is empty; otherwise returns FALSE.
Matches the sequence with \fIseq\fR. Returns TQt::Identical if successful, TQt::PartialMatch for matching but incomplete \fIseq\fR, and TQt::NoMatch if the sequences have nothing in common. Returns TQt::NoMatch if \fIseq\fR is shorter.
.SH "QKeySequence::operator TQString () const"
Creates an accelerator string for the key sequence. For instance CTRL+Key_O gives "Ctrl+O". If the key sequence has multiple key codes they are returned comma-separated, e.g." Alt+X, Ctrl+Y, Z". The strings, "Ctrl", "Shift", etc. are translated (using TQObject::tr()) in the "QAccel" scope. If the key sequence has no keys, TQString::null is returned.
Creates an accelerator string for the key sequence. For instance CTRL+Key_O gives "Ctrl+O". If the key sequence has multiple key codes they are returned comma-separated, e.g." Alt+X, Ctrl+Y, Z". The strings, "Ctrl", "Shift", etc. are translated (using TQObject::tr()) in the "TQAccel" scope. If the key sequence has no keys, TQString::null is returned.
.PP
On Mac OS X, the string returned resembles the sequence that is shown in the menubar.
@ -161,7 +161,7 @@ The look of a TQLabel can be tuned in several ways. All the settings of TQFrame
.br
.fi
.PP
A TQLabel is often used as a label for an interactive widget. For this use TQLabel provides a useful mechanism for adding an accelerator key (see QAccel) that will set the keyboard focus to the other widget (called the TQLabel's "buddy"). For example:
A TQLabel is often used as a label for an interactive widget. For this use TQLabel provides a useful mechanism for adding an accelerator key (see TQAccel) that will set the keyboard focus to the other widget (called the TQLabel's "buddy"). For example:
.PP
.nf
.br
@ -279,7 +279,7 @@ With the code above, the focus jumps to the Name field when the user presses Alt
.PP
To unset a previously set buddy, call this function with \fIbuddy\fR set to 0.
.PP
See also buddy(), text, QAccel, and alignment.
See also buddy(), text, TQAccel, and alignment.
.PP
Examples:
.)l addressbook/centralwidget.cpp, chart/optionsform.cpp, and regexptester/regexptester.cpp.
@ -97,10 +97,10 @@ Inherits TQFrame and TQMenuData.
.BI "int \fBinsertItem\fR ( TQWidget * widget, int id = -1, int index = -1 )"
.br
.ti -1c
.BI "int \fBinsertItem\fR ( const TQIconSet & icon, QCustomMenuItem * custom, int id = -1, int index = -1 )"
.BI "int \fBinsertItem\fR ( const TQIconSet & icon, TQCustomMenuItem * custom, int id = -1, int index = -1 )"
.br
.ti -1c
.BI "int \fBinsertItem\fR ( QCustomMenuItem * custom, int id = -1, int index = -1 )"
.BI "int \fBinsertItem\fR ( TQCustomMenuItem * custom, int id = -1, int index = -1 )"
.br
.ti -1c
.BI "int \fBinsertSeparator\fR ( int index = -1 )"
@ -198,7 +198,7 @@ Example (from action/application.cpp):
fileNewAction->addTo( file );
.fi
.PP
Menu items can have text and pixmaps (or iconsets), see the various insertItem() overloads, as well as separators, see insertSeparator(). You can also add custom menu items that are derived from QCustomMenuItem.
Menu items can have text and pixmaps (or iconsets), see the various insertItem() overloads, as well as separators, see insertSeparator(). You can also add custom menu items that are derived from TQCustomMenuItem.
.PP
Menu items may be removed with removeItem() and enabled or disabled with setItemEnabled().
.PP
@ -225,7 +225,7 @@ l - l. String matches Placement Notes about.* Application Menu | About If this e
.PP
menu/menu.cpp is an example of TQMenuBar and TQPopupMenu use.
.PP
See also TQPopupMenu, QAccel, TQAction, Aqua Style Guidelines, GUI Design Handbook: Menu Bar, and Main Window and Related Classes.
See also TQPopupMenu, TQAccel, TQAction, Aqua Style Guidelines, GUI Design Handbook: Menu Bar, and Main Window and Related Classes.
.SS "Member Type Documentation"
.SH "TQMenuBar::Separator"
This enum type is used to decide whether TQMenuBar should draw a separator line at its bottom.
@ -278,7 +278,7 @@ See also activated() and TQMenuData::insertItem().
.SH "int TQMenuData::insertItem ( const TQString & text, const TQObject * receiver, const char * member, const QKeySequence & accel = 0, int id = -1, int index = -1 )"
The family of insertItem() functions inserts menu items into a popup menu or a menu bar.
.PP
A menu item is usually either a text string or a pixmap, both with an optional icon or keyboard accelerator. For special cases it is also possible to insert custom items (see QCustomMenuItem) or even widgets into popup menus.
A menu item is usually either a text string or a pixmap, both with an optional icon or keyboard accelerator. For special cases it is also possible to insert custom items (see TQCustomMenuItem) or even widgets into popup menus.
.PP
Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar.
.PP
@ -322,7 +322,7 @@ The \fIid\fR specifies the identification number associated with the menu item.
.PP
The \fIindex\fR specifies the position in the menu. The menu item is appended at the end of the list if \fIindex\fR is negative.
.PP
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent TQAccel object.
.PP
\fBWarning:\fR Be careful when passing a literal 0 to insertItem() because some C++ compilers choose the wrong overloaded function. Cast the 0 to what you mean, e.g. \fC(TQObject*)0\fR.
.PP
@ -330,7 +330,7 @@ Note that keyboard accelerators in TQt are not application-global, instead they
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.PP
Examples:
.)l addressbook/mainwindow.cpp, canvas/canvas.cpp, menu/menu.cpp, qwerty/qwerty.cpp, scrollview/scrollview.cpp, showimg/showimg.cpp, and sound/sound.cpp.
@ -341,7 +341,7 @@ Inserts a menu item with icon \fIicon\fR, text \fItext\fR, accelerator \fIaccel\
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.SH "int TQMenuData::insertItem ( const TQPixmap & pixmap, const TQObject * receiver, const char * member, const QKeySequence & accel = 0, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@ -361,7 +361,7 @@ To look best when being highlighted as a menu item, the pixmap should provide a
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.SH "int TQMenuData::insertItem ( const TQString & text, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@ -464,7 +464,7 @@ If the widget is focus-enabled it will get focus when the user traverses the pop
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem().
.SH "int TQMenuData::insertItem ( const TQIconSet & icon, QCustomMenuItem * custom, int id = -1, int index = -1 )"
.SH "int TQMenuData::insertItem ( const TQIconSet & icon, TQCustomMenuItem * custom, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Inserts a custom menu item \fIcustom\fR with an \fIicon\fR and with optional id \fIid\fR, and optional \fIindex\fR position.
@ -475,8 +475,8 @@ If you want to connect a custom item to a slot, use connectItem().
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also connectItem(), removeItem(), and QCustomMenuItem.
.SH "int TQMenuData::insertItem ( QCustomMenuItem * custom, int id = -1, int index = -1 )"
See also connectItem(), removeItem(), and TQCustomMenuItem.
.SH "int TQMenuData::insertItem ( TQCustomMenuItem * custom, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Inserts a custom menu item \fIcustom\fR with optional id \fIid\fR, and optional \fIindex\fR position.
@ -487,7 +487,7 @@ If you want to connect a custom item to a slot, use connectItem().
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also connectItem(), removeItem(), and QCustomMenuItem.
See also connectItem(), removeItem(), and TQCustomMenuItem.
.SH "int TQMenuData::insertSeparator ( int index = -1 )"
Inserts a separator at position \fIindex\fR, and returns the menu identifier number allocated to it. The separator becomes the last menu item if \fIindex\fR is negative.
.SH "int TQMenuData::insertItem ( const TQString & text, const TQObject * receiver, const char * member, const QKeySequence & accel = 0, int id = -1, int index = -1 )"
The family of insertItem() functions inserts menu items into a popup menu or a menu bar.
.PP
A menu item is usually either a text string or a pixmap, both with an optional icon or keyboard accelerator. For special cases it is also possible to insert custom items (see QCustomMenuItem) or even widgets into popup menus.
A menu item is usually either a text string or a pixmap, both with an optional icon or keyboard accelerator. For special cases it is also possible to insert custom items (see TQCustomMenuItem) or even widgets into popup menus.
.PP
Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar.
.PP
@ -362,7 +362,7 @@ The \fIid\fR specifies the identification number associated with the menu item.
.PP
The \fIindex\fR specifies the position in the menu. The menu item is appended at the end of the list if \fIindex\fR is negative.
.PP
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent TQAccel object.
.PP
\fBWarning:\fR Be careful when passing a literal 0 to insertItem() because some C++ compilers choose the wrong overloaded function. Cast the 0 to what you mean, e.g. \fC(TQObject*)0\fR.
.PP
@ -370,7 +370,7 @@ Note that keyboard accelerators in TQt are not application-global, instead they
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.PP
Examples:
.)l addressbook/mainwindow.cpp, canvas/canvas.cpp, menu/menu.cpp, qwerty/qwerty.cpp, scrollview/scrollview.cpp, showimg/showimg.cpp, and sound/sound.cpp.
@ -381,7 +381,7 @@ Inserts a menu item with icon \fIicon\fR, text \fItext\fR, accelerator \fIaccel\
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.SH "int TQMenuData::insertItem ( const TQPixmap & pixmap, const TQObject * receiver, const char * member, const QKeySequence & accel = 0, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@ -401,7 +401,7 @@ To look best when being highlighted as a menu item, the pixmap should provide a
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.SH "int TQMenuData::insertItem ( const TQString & text, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@ -504,7 +504,7 @@ If the widget is focus-enabled it will get focus when the user traverses the pop
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem().
.SH "int TQMenuData::insertItem ( const TQIconSet & icon, QCustomMenuItem * custom, int id = -1, int index = -1 )"
.SH "int TQMenuData::insertItem ( const TQIconSet & icon, TQCustomMenuItem * custom, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Inserts a custom menu item \fIcustom\fR with an \fIicon\fR and with optional id \fIid\fR, and optional \fIindex\fR position.
@ -515,8 +515,8 @@ If you want to connect a custom item to a slot, use connectItem().
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also connectItem(), removeItem(), and QCustomMenuItem.
.SH "int TQMenuData::insertItem ( QCustomMenuItem * custom, int id = -1, int index = -1 )"
See also connectItem(), removeItem(), and TQCustomMenuItem.
.SH "int TQMenuData::insertItem ( TQCustomMenuItem * custom, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Inserts a custom menu item \fIcustom\fR with optional id \fIid\fR, and optional \fIindex\fR position.
@ -527,7 +527,7 @@ If you want to connect a custom item to a slot, use connectItem().
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also connectItem(), removeItem(), and QCustomMenuItem.
See also connectItem(), removeItem(), and TQCustomMenuItem.
.SH "int TQMenuData::insertSeparator ( int index = -1 )"
Inserts a separator at position \fIindex\fR, and returns the menu identifier number allocated to it. The separator becomes the last menu item if \fIindex\fR is negative.
.PP
@ -591,7 +591,7 @@ An accelerator key consists of a key code and a combination of the modifiers \fC
.PP
Defining an accelerator key produces a text that is added to the menu item; for instance, \fCCTRL\fR + \fCKey_O\fR produces "Ctrl+O". The text is formatted differently for different platforms.
.PP
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent TQAccel object.
.PP
Example:
.PP
@ -623,7 +623,7 @@ If you need to translate accelerators, use tr() with a string:
.PP
You can also specify the accelerator in the insertItem() function. You may prefer to use TQAction to associate accelerators with menu items.
.PP
See also accel(), insertItem(), QAccel, and TQAction.
See also accel(), insertItem(), TQAccel, and TQAction.
.PP
Example: menu/menu.cpp.
.SH "void TQMenuData::setId ( int index, int id )\fC [virtual]\fR"
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QMotif class provides the basis of the Motif Extension.
The TQMotif class provides the basis of the Motif Extension.
.PP
QMotif only provides a few public functions, but it is at the heart of the integration. QMotif is responsible for initializing the Xt toolkit and the Xt application context. It does not open a connection to the X server, that is done by QApplication.
TQMotif only provides a few public functions, but it is at the heart of the integration. TQMotif is responsible for initializing the Xt toolkit and the Xt application context. It does not open a connection to the X server, that is done by QApplication.
.PP
The only member function in QMotif that depends on an X server connection is QMotif::initialize(). QMotif must be created before QApplication.
The only member function in TQMotif that depends on an X server connection is TQMotif::initialize(). TQMotif must be created before QApplication.
.PP
Example usage of QMotif and QApplication:
Example usage of TQMotif and QApplication:
.PP
.nf
.br
@ -57,7 +57,7 @@ Example usage of QMotif and QApplication:
Creates TQMotif, which allows TQt and Xt/Motif integration.
.PP
If \fIcontext\fR is 0, QMotif creates a default application context itself. The context is accessible through applicationContext().
If \fIcontext\fR is 0, TQMotif creates a default application context itself. The context is accessible through applicationContext().
.PP
All arguments passed to this function (\fIapplicationClass\fR, \fIoptions\fR and \fInumOptions\fR) are used to call XtDisplayInitialize() after QApplication has been constructed.
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QMotifDialog class provides the TQDialog API for Motif-based dialogs.
The TQMotifDialog class provides the TQDialog API for Motif-based dialogs.
.PP
QMotifDialog provides two separate modes of operation. The application programmer can use QMotifDialog with an existing Motif-based dialog and a TQWidget parent, or the application programmer can use QMotifDialog with a custom Qt-based dialog and a Motif-based parent. Modality continues to work as expected.
TQMotifDialog provides two separate modes of operation. The application programmer can use TQMotifDialog with an existing Motif-based dialog and a TQWidget parent, or the application programmer can use TQMotifDialog with a custom Qt-based dialog and a Motif-based parent. Modality continues to work as expected.
.PP
Motif-based dialogs must have a \fCShell\fR widget parent with a single child, due to requirements of the Motif toolkit. The \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR, is created during construction. It can be accessed using the shell() member function.
.PP
The single child of the \fCShell\fR can be accessed using the dialog() member function \fIafter\fR it has been created.
.PP
The acceptCallback() and rejectCallback() functions provide a convenient way to call TQDialog::accept() and TQDialog::reject() through callbacks. A pointer to the QMotifDialog should be passed as the \fCclient_data\fR argument to the callback.
The acceptCallback() and rejectCallback() functions provide a convenient way to call TQDialog::accept() and TQDialog::reject() through callbacks. A pointer to the TQMotifDialog should be passed as the \fCclient_data\fR argument to the callback.
.PP
The API and behavior QMotifDialog is identical to that of TQDialog when using a custom Qt-based dialog with a Motif-based parent. The only difference is that a Motif-based \fIparent\fR argument is passed to the constructor, instead of a TQWidget parent.
The API and behavior TQMotifDialog is identical to that of TQDialog when using a custom Qt-based dialog with a Motif-based parent. The only difference is that a Motif-based \fIparent\fR argument is passed to the constructor, instead of a TQWidget parent.
.SS "Member Type Documentation"
.SH "QMotifDialog::DialogType"
.SH "TQMotifDialog::DialogType"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
This enum lists the predefined Motif dialog types.
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Creates a QMotifDialog using one of the predefined Motif dialog types. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
Creates a TQMotifDialog using one of the predefined Motif dialog types. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
.PP
This constructor creates a Shell widget, which is a special subclass of XmDialogShell. The \fIparent\fR, \fIargs\fR and \fIargcount\fR arguments are passed to XtCreatePopupShell() when creating the subclass. You can access the Shell widget with the shell() member function.
.PP
This constructor also creates the dialog widget with the Shell widget as its parent. The type of the dialog created is specified by the \fIdialogtype\fR argument. See the DialogType enum for a list of available dialog types. You can access the dialog widget with the dialog() member function.
.PP
\fBWarning:\fR QMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself.
\fBWarning:\fR TQMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself.
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Creates a QMotifDialog which allows the application programmer to use the Motif-based \fIparent\fR for a custom TQDialog. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
Creates a TQMotifDialog which allows the application programmer to use the Motif-based \fIparent\fR for a custom TQDialog. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
.PP
This constructor creates a Shell widget, which is a special subclass of XmDialogShell. The \fIargs\fR and \fIargcount\fR arguments are passed to XtCreatePopupShell() when creating the subclass. You can access the Shell widget with the shell() member function.
.PP
The dialog widget is not created by the constructor. You must create the dialog widget as a child of the the widget returned by shell(). You can access the child widget with the dialog() member function.
.PP
A dialog widget is not created by this constructor. Instead, you should create the dialog widget as a child of this dialog. QMotifDialog will take ownership of your custom dialog, and you can access it with the dialog() member function.
A dialog widget is not created by this constructor. Instead, you should create the dialog widget as a child of this dialog. TQMotifDialog will take ownership of your custom dialog, and you can access it with the dialog() member function.
.PP
\fBWarning:\fR QMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself.
\fBWarning:\fR TQMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself.
Creates a QMotifDialog which allows the application programmer to use the Motif-based \fIparent\fR for a custom TQDialog. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
Creates a TQMotifDialog which allows the application programmer to use the Motif-based \fIparent\fR for a custom TQDialog. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
.PP
This constructor creates a \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR. You can access the \fCShell\fR widget with the shell() member function.
Creates a QMotifDialog which allows the application programmer to use a TQWidget parent for an existing Motif-based dialog. The \fIparent\fR, \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
Creates a TQMotifDialog which allows the application programmer to use a TQWidget parent for an existing Motif-based dialog. The \fIparent\fR, \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor.
.PP
This constructor creates a \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR. You can access the \fCShell\fR widget with the shell() member functon.
.PP
A dialog widget is not created by this constructor. Instead, you should create the dialog widget as a child of this dialog. QMotifDialog will take ownership of your custom dialog, and you can access it with the dialog() member function.
A dialog widget is not created by this constructor. Instead, you should create the dialog widget as a child of this dialog. TQMotifDialog will take ownership of your custom dialog, and you can access it with the dialog() member function.
.PP
\fBWarning:\fR QMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself.
\fBWarning:\fR TQMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself.
@ -28,30 +28,30 @@ Inherited by QCDEStyle, QMotifPlusStyle, and QSGIStyle.
.br
.in -1c
.SH DESCRIPTION
The QMotifStyle class provides Motif look and feel.
The TQMotifStyle class provides Motif look and feel.
.PP
This class implements the Motif look and feel. It closely resembles the original Motif look as defined by the Open Group, but with some minor improvements. The Motif style is Qt's default GUI style on UNIX platforms.
If \fIuseHighlightCols\fR is FALSE (the default), the style will polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color.
If \fIarg\fR is FALSE, the style will polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color.
.PP
The effect will show up the next time an application palette is set via QApplication::setPalette(). The current color palette of the application remains unchanged.
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QMotifWidget class provides the TQWidget API for Xt/Motif widgets.
The TQMotifWidget class provides the TQWidget API for Xt/Motif widgets.
.PP
QMotifWidget exists to provide a TQWidget that can act as a parent for any Xt/Motif widget. Since the QMotifWidget is a proper TQWidget, it can be used as a top-level widget (e.g. 0 parent) or as a child of any other TQWidget. Note: Since QMotifWidget acts as a parent for Xt/Motif widgets, you should not create TQWidgets with a QMotifWidget parent.
TQMotifWidget exists to provide a TQWidget that can act as a parent for any Xt/Motif widget. Since the TQMotifWidget is a proper TQWidget, it can be used as a top-level widget (e.g. 0 parent) or as a child of any other TQWidget. Note: Since TQMotifWidget acts as a parent for Xt/Motif widgets, you should not create TQWidgets with a TQMotifWidget parent.
.PP
An Xt/Motif widget with a top-level QMotifWidget parent can begin using the standard TQt dialogs and custom TQDialogs while keeping the main Xt/Motif interface of the application. Using a QMotifWidget as the parent for the various TQDialogs will ensure that modality and stacking works properly throughout the entire application.
An Xt/Motif widget with a top-level TQMotifWidget parent can begin using the standard TQt dialogs and custom TQDialogs while keeping the main Xt/Motif interface of the application. Using a TQMotifWidget as the parent for the various TQDialogs will ensure that modality and stacking works properly throughout the entire application.
.PP
Applications moving to TQt may have custom Xt/Motif widgets that will take time to rewrite with Qt. Such applications can use these custom widgets as QMotifWidget with TQWidget parents. This allows the application's interface to be replaced gradually.
Applications moving to TQt may have custom Xt/Motif widgets that will take time to rewrite with Qt. Such applications can use these custom widgets as TQMotifWidget with TQWidget parents. This allows the application's interface to be replaced gradually.
.PP
\fBWarning:\fR QMotifWidget uses the X11 window ID of the Motif widget directly, instead of creating its own. Because ot this, TQWidget::reparent() will not work. This includes the functions TQWidget::showFullScreen() and TQWidget::showNormal(), which use TQWidget::reparent().
\fBWarning:\fR TQMotifWidget uses the X11 window ID of the Motif widget directly, instead of creating its own. Because ot this, TQWidget::reparent() will not work. This includes the functions TQWidget::showFullScreen() and TQWidget::showNormal(), which use TQWidget::reparent().
Creates a TQMotifWidget of the given \fIwidgetclass\fR as a child of \fIparent\fR, with the name \fIname\fR and widget flags \fIflags\fR.
.PP
The \fIargs\fR and \fIargcount\fR arguments are passed on to XtCreateWidget.
.PP
The motifWidget() function returns the resulting Xt/Motif widget. This widget can be used as a parent for any other Xt/Motif widget.
.PP
If \fIparent\fR is a QMotifWidget, the Xt/Motif widget is created as a child of the parent's motifWidget(). If \ parent is 0 or a normal TQWidget, the Xt/Motif widget is created as a child of a special TopLevelShell widget. Xt/Motif widgets can use this special TopLevelShell parent as the parent for existing Xt/Motif dialogs or QMotifDialogs.
Destroys the QMotifWidget. The special TopLevelShell is also destroyed, if it was created during construction.
.SH "Widget QMotifWidget::motifWidget () const"
If \fIparent\fR is a TQMotifWidget, the Xt/Motif widget is created as a child of the parent's motifWidget(). If \ parent is 0 or a normal TQWidget, the Xt/Motif widget is created as a child of a special TopLevelShell widget. Xt/Motif widgets can use this special TopLevelShell parent as the parent for existing Xt/Motif dialogs or TQMotifDialogs.
@ -75,7 +75,7 @@ The TQWidget::setEnabled() function can be used to enable or disable mouse and k
.PP
The event handlers TQWidget::mousePressEvent(), TQWidget::mouseReleaseEvent(), TQWidget::mouseDoubleClickEvent() and TQWidget::mouseMoveEvent() receive mouse events.
.PP
See also TQWidget::mouseTracking, TQWidget::grabMouse(), QCursor::pos(), and Event Classes.
See also TQWidget::mouseTracking, TQWidget::grabMouse(), TQCursor::pos(), and Event Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QMouseEvent::QMouseEvent ( Type type, const TQPoint & pos, int button, int state )"
Constructs a mouse event object.
@ -84,7 +84,7 @@ The \fItype\fR parameter must be one of TQEvent::MouseButtonPress, TQEvent::Mous
.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
The globalPos() is initialized to QCursor::pos(), which may not be appropriate. Use the other constructor to specify the global position explicitly.
The globalPos() is initialized to TQCursor::pos(), which may not be appropriate. Use the other constructor to specify the global position explicitly.
.SH "QMouseEvent::QMouseEvent ( Type type, const TQPoint & pos, const TQPoint & globalPos, int button, int state )"
Constructs a mouse event object.
.PP
@ -111,7 +111,7 @@ See also state() and TQt::ButtonState.
Examples:
.)l dclock/dclock.cpp, life/life.cpp, and t14/cannon.cpp.
Returns the global position of the mouse pointer \fIat the time of the event\fR. This is important on asynchronous window systems like X11. Whenever you move your widgets around in response to mouse events, globalPos() may differ a lot from the current pointer position QCursor::pos(), and from TQWidget::mapToGlobal( pos() ).
Returns the global position of the mouse pointer \fIat the time of the event\fR. This is important on asynchronous window systems like X11. Whenever you move your widgets around in response to mouse events, globalPos() may differ a lot from the current pointer position TQCursor::pos(), and from TQWidget::mapToGlobal( pos() ).
.BI "virtual void \fBconnectNotify\fR ( const char * signal )"
@ -203,7 +203,7 @@ TQObjects organize themselves in object trees. When you create a TQObject with a
.PP
Every object has an object name() and can report its className() and whether it inherits() another class in the TQObject inheritance hierarchy.
.PP
When an object is deleted, it emits a destroyed() signal. You can catch this signal to avoid dangling references to TQObjects. The QGuardedPtr class provides an elegant way to use this feature.
When an object is deleted, it emits a destroyed() signal. You can catch this signal to avoid dangling references to TQObjects. The TQGuardedPtr class provides an elegant way to use this feature.
.PP
TQObjects can receive events through event() and filter the events of other objects. See installEventFilter() and eventFilter() for details. A convenience handler, childEvent(), can be reimplemented to catch child events.
.PP
@ -254,7 +254,7 @@ Searches the children and optionally grandchildren of this object, and returns a
If \fIrecursiveSearch\fR is TRUE (the default), child() performs a depth-first search of the object's children.
.PP
If there is no such object, this function returns 0. If there are more than one, the first one found is retured; if you need all of them, use queryList().
@ -381,10 +381,10 @@ This virtual function is called when something has been connected to \fIsignal\f
\fBWarning:\fR This function violates the object-oriented principle of modularity. However, it might be useful when you need to perform expensive initialization only if something is connected to a signal.
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.
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 TQCustomEvent or TQCustomEvent subclass.
.PP
See also event() and QCustomEvent.
See also event() and TQCustomEvent.
.SH "void TQObject::deleteLater ()\fC [slot]\fR"
Performs a deferred deletion of this object.
.PP
@ -583,7 +583,7 @@ Notice in the example above that unhandled events are passed to the base class's
.PP
See also installEventFilter().
.PP
Reimplemented in QAccel, TQScrollView, and TQSpinBox.
Reimplemented in TQAccel, TQScrollView, and TQSpinBox.
.SH "bool TQObject::highPriority () const"
Returns TRUE if the object is a high-priority object, or FALSE if it is a standard-priority object.
.PP
@ -701,7 +701,7 @@ And here's how to install it on two widgets:
.br
.fi
.PP
The QAccel class, for example, uses this technique to intercept accelerator key presses.
The TQAccel class, for example, uses this technique to intercept accelerator key presses.
.PP
\fBWarning:\fR If you delete the receiver object in your eventFilter() function, be sure to return TRUE. If you return FALSE, TQt sends the event to the deleted object and the program will crash.
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,16 +7,16 @@
.ad l
.nh
.SH NAME
QPlatinumStyle \- Mac/Platinum look and feel
TQPlatinumStyle \- Mac/Platinum look and feel
.SH SYNOPSIS
\fC#include <ntqplatinumstyle.h>\fR
\fC#include <tqplatinumstyle.h>\fR
.PP
Inherits QWindowsStyle.
Inherits TQWindowsStyle.
.PP
.SS "Public Members"
.in +1c
.ti -1c
.BI "\fBQPlatinumStyle\fR ()"
.BI "\fBTQPlatinumStyle\fR ()"
.br
.in -1c
.SS "Protected Members"
@ -29,21 +29,21 @@ Inherits QWindowsStyle.
.br
.in -1c
.SH DESCRIPTION
The QPlatinumStyle class provides Mac/Platinum look and feel.
The TQPlatinumStyle class provides Mac/Platinum look and feel.
.PP
This class implements the Platinum look and feel. It's an experimental class that tries to resemble a Macinosh-like GUI style with the TQStyle system. The emulation is currently far from perfect.
.PP
See also QAquaStyle and Widget Appearance and Style.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QPlatinumStyle::QPlatinumStyle ()"
Constructs a QPlatinumStyle
.SH "void QPlatinumStyle::drawRiffles ( TQPainter * p, int x, int y, int w, int h, const TQColorGroup & g, bool horizontal ) const\fC [protected]\fR"
.SH "TQPlatinumStyle::TQPlatinumStyle ()"
Constructs a TQPlatinumStyle
.SH "void TQPlatinumStyle::drawRiffles ( TQPainter * p, int x, int y, int w, int h, const TQColorGroup & g, bool horizontal ) const\fC [protected]\fR"
Draws the nifty Macintosh decoration used on sliders using painter \fIp\fR and colorgroup \fIg\fR. \fIx\fR, \fIy\fR, \fIw\fR, \fIh\fR and \fIhorizontal\fR specify the geometry and orientation of the riffles.
@ -109,10 +109,10 @@ Inherits TQFrame and TQMenuData.
.BI "int \fBinsertItem\fR ( TQWidget * widget, int id = -1, int index = -1 )"
.br
.ti -1c
.BI "int \fBinsertItem\fR ( const TQIconSet & icon, QCustomMenuItem * custom, int id = -1, int index = -1 )"
.BI "int \fBinsertItem\fR ( const TQIconSet & icon, TQCustomMenuItem * custom, int id = -1, int index = -1 )"
.br
.ti -1c
.BI "int \fBinsertItem\fR ( QCustomMenuItem * custom, int id = -1, int index = -1 )"
.BI "int \fBinsertItem\fR ( TQCustomMenuItem * custom, int id = -1, int index = -1 )"
.br
.ti -1c
.BI "int \fBinsertSeparator\fR ( int index = -1 )"
@ -219,7 +219,7 @@ The TQPopupMenu class provides a popup menu widget.
.PP
A popup menu widget is a selection menu. It can be either a pull-down menu in a menu bar or a standalone context (popup) menu. Pull-down menus are shown by the menu bar when the user clicks on the respective item or presses the specified shortcut key. Use TQMenuBar::insertItem() to insert a popup menu into a menu bar. Show a context menu either asynchronously with popup() or synchronously with exec().
.PP
Technically, a popup menu consists of a list of menu items. You add items with insertItem(). An item is either a string, a pixmap or a custom item that provides its own drawing function (see QCustomMenuItem). In addition, items can have an optional icon drawn on the very left side and an accelerator key such as" Ctrl+X".
Technically, a popup menu consists of a list of menu items. You add items with insertItem(). An item is either a string, a pixmap or a custom item that provides its own drawing function (see TQCustomMenuItem). In addition, items can have an optional icon drawn on the very left side and an accelerator key such as" Ctrl+X".
.PP
There are three kinds of menu items: separators, menu items that perform an action and menu items that show a submenu. Separators are inserted with insertSeparator(). For submenus, you pass a pointer to a TQPopupMenu in your call to insertItem(). All other items are considered action items.
.PP
@ -269,7 +269,7 @@ Example: mdi/application.cpp.
.SH "QKeySequence TQMenuData::accel ( int id ) const"
Returns the accelerator key that has been defined for the menu item \fIid\fR, or 0 if it has no accelerator key or if there is no such menu item.
.PP
See also setAccel(), QAccel, and ntqnamespace.h.
See also setAccel(), TQAccel, and ntqnamespace.h.
.SH "void TQPopupMenu::activated ( int id )\fC [signal]\fR"
This signal is emitted when a menu item is selected; \fIid\fR is the id of the selected item.
.PP
@ -343,7 +343,7 @@ This is equivalent to \fCexec(mapToGlobal(TQPoint(0,0)))\fR. In most situations
.PP
.nf
.br
exec(QCursor::pos());
exec(TQCursor::pos());
.br
.fi
or aligned to a widget:
@ -371,7 +371,7 @@ Common usage is to position the popup at the current mouse position:
.PP
.nf
.br
exec( QCursor::pos() );
exec( TQCursor::pos() );
.br
.fi
or aligned to a widget:
@ -406,7 +406,7 @@ Returns the id of the item at \fIpos\fR, or -1 if there is no item there or if i
.SH "int TQMenuData::insertItem ( const TQString & text, const TQObject * receiver, const char * member, const QKeySequence & accel = 0, int id = -1, int index = -1 )"
The family of insertItem() functions inserts menu items into a popup menu or a menu bar.
.PP
A menu item is usually either a text string or a pixmap, both with an optional icon or keyboard accelerator. For special cases it is also possible to insert custom items (see QCustomMenuItem) or even widgets into popup menus.
A menu item is usually either a text string or a pixmap, both with an optional icon or keyboard accelerator. For special cases it is also possible to insert custom items (see TQCustomMenuItem) or even widgets into popup menus.
.PP
Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar.
.PP
@ -450,7 +450,7 @@ The \fIid\fR specifies the identification number associated with the menu item.
.PP
The \fIindex\fR specifies the position in the menu. The menu item is appended at the end of the list if \fIindex\fR is negative.
.PP
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent TQAccel object.
.PP
\fBWarning:\fR Be careful when passing a literal 0 to insertItem() because some C++ compilers choose the wrong overloaded function. Cast the 0 to what you mean, e.g. \fC(TQObject*)0\fR.
.PP
@ -458,7 +458,7 @@ Note that keyboard accelerators in TQt are not application-global, instead they
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.PP
Examples:
.)l addressbook/mainwindow.cpp, canvas/canvas.cpp, menu/menu.cpp, qwerty/qwerty.cpp, scrollview/scrollview.cpp, showimg/showimg.cpp, and sound/sound.cpp.
@ -469,7 +469,7 @@ Inserts a menu item with icon \fIicon\fR, text \fItext\fR, accelerator \fIaccel\
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.SH "int TQMenuData::insertItem ( const TQPixmap & pixmap, const TQObject * receiver, const char * member, const QKeySequence & accel = 0, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@ -489,7 +489,7 @@ To look best when being highlighted as a menu item, the pixmap should provide a
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem(), changeItem(), setAccel(), connectItem(), QAccel, and ntqnamespace.h.
See also removeItem(), changeItem(), setAccel(), connectItem(), TQAccel, and ntqnamespace.h.
.SH "int TQMenuData::insertItem ( const TQString & text, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
@ -592,7 +592,7 @@ If the widget is focus-enabled it will get focus when the user traverses the pop
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also removeItem().
.SH "int TQMenuData::insertItem ( const TQIconSet & icon, QCustomMenuItem * custom, int id = -1, int index = -1 )"
.SH "int TQMenuData::insertItem ( const TQIconSet & icon, TQCustomMenuItem * custom, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Inserts a custom menu item \fIcustom\fR with an \fIicon\fR and with optional id \fIid\fR, and optional \fIindex\fR position.
@ -603,8 +603,8 @@ If you want to connect a custom item to a slot, use connectItem().
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also connectItem(), removeItem(), and QCustomMenuItem.
.SH "int TQMenuData::insertItem ( QCustomMenuItem * custom, int id = -1, int index = -1 )"
See also connectItem(), removeItem(), and TQCustomMenuItem.
.SH "int TQMenuData::insertItem ( TQCustomMenuItem * custom, int id = -1, int index = -1 )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Inserts a custom menu item \fIcustom\fR with optional id \fIid\fR, and optional \fIindex\fR position.
@ -615,7 +615,7 @@ If you want to connect a custom item to a slot, use connectItem().
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
See also connectItem(), removeItem(), and QCustomMenuItem.
See also connectItem(), removeItem(), and TQCustomMenuItem.
.SH "int TQMenuData::insertSeparator ( int index = -1 )"
Inserts a separator at position \fIindex\fR, and returns the menu identifier number allocated to it. The separator becomes the last menu item if \fIindex\fR is negative.
.PP
@ -687,7 +687,7 @@ An accelerator key consists of a key code and a combination of the modifiers SHI
.PP
Defining an accelerator key produces a text that is added to the menu item; for instance, CTRL + Key_O produces "Ctrl+O". The text is formatted differently for different platforms.
.PP
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in TQPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent TQAccel object.
.PP
Example:
.PP
@ -719,7 +719,7 @@ If you need to translate accelerators, use tr() with a string:
.PP
You can also specify the accelerator in the insertItem() function. You may prefer to use TQAction to associate accelerators with menu items.
.PP
See also accel(), insertItem(), QAccel, and TQAction.
See also accel(), insertItem(), TQAccel, and TQAction.
.PP
Example: menu/menu.cpp.
.SH "void TQPopupMenu::setActiveItem ( int i )\fC [virtual]\fR"
.BI "virtual void \fBcontentsWheelEvent\fR ( QWheelEvent * e )"
.br
.ti -1c
.BI "virtual void \fBcontentsContextMenuEvent\fR ( QContextMenuEvent * e )"
.BI "virtual void \fBcontentsContextMenuEvent\fR ( TQContextMenuEvent * e )"
.br
.ti -1c
.BI "virtual void \fBviewportPaintEvent\fR ( TQPaintEvent * pe )"
@ -517,7 +517,7 @@ Returns the clipper widget. Contents in the scrollview are ultimately clipped to
You should not need to use this function.
.PP
See also visibleWidth and visibleHeight.
.SH "void TQScrollView::contentsContextMenuEvent ( QContextMenuEvent * e )\fC [virtual protected]\fR"
.SH "void TQScrollView::contentsContextMenuEvent ( TQContextMenuEvent * e )\fC [virtual protected]\fR"
This event handler is called whenever the TQScrollView receives a contextMenuEvent() in \fIe\fR: the mouse position is translated to be a point on the contents.
If \fIuseHighlightCols\fR is FALSE (default value), the style will polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color.
.PP
See also QMotifStyle::useHighlightColors().
.SH "QSGIStyle::~QSGIStyle ()\fC [virtual]\fR"
See also TQMotifStyle::useHighlightColors().
.SH "TQSGIStyle::~TQSGIStyle ()\fC [virtual]\fR"
Destroys the style.
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqsgistyle.html
.BR http://doc.trolltech.com/tqsgistyle.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
Returns the global position of the device \fIat the time of the event\fR. This is important on asynchronous windows systems like X11; whenever you move your widgets around in response to mouse events, globalPos() can differ significantly from the current position QCursor::pos().
Returns the global position of the device \fIat the time of the event\fR. This is important on asynchronous windows systems like X11; whenever you move your widgets around in response to mouse events, globalPos() can differ significantly from the current position TQCursor::pos().
@ -68,7 +68,7 @@ TQWhatsThis provides a single window with an explanatory text that pops up when
.PP
(Note that if there is an accelerator for Shift+F1, this mechanism will not work.)
.PP
To add "What's this?" text to a widget you simply call TQWhatsThis::add() for the widget. For example, to assign text to a menu item, call TQMenuData::setWhatsThis(); for a global accelerator key, call QAccel::setWhatsThis() and If you're using actions, use TQAction::setWhatsThis().
To add "What's this?" text to a widget you simply call TQWhatsThis::add() for the widget. For example, to assign text to a menu item, call TQMenuData::setWhatsThis(); for a global accelerator key, call TQAccel::setWhatsThis() and If you're using actions, use TQAction::setWhatsThis().
.PP
The text can be either rich text or plain text. If you specify a rich text formatted string, it will be rendered using the default stylesheet. This makes it possible to embed images. See TQStyleSheet::defaultSheet() for details.
.PP
@ -128,7 +128,7 @@ This virtual function is called when the user clicks inside the" What's this?" w
If the function returns TRUE (the default), the "What's this?" window is closed, otherwise it remains visible.
.PP
The default implementation ignores \fIhref\fR and returns TRUE.
Display \fItext\fR in a help window at the global screen position \fIpos\fR.
.PP
If widget \fIw\fR is not 0 and has its own dedicated TQWhatsThis object, this object will receive clicked() messages when the user clicks on hyperlinks inside the help text.
@ -146,7 +146,7 @@ See also inWhatsThisMode() and leaveWhatsThisMode().
Returns TRUE if the application is in "What's this?" mode; otherwise returns FALSE.
.PP
See also enterWhatsThisMode() and leaveWhatsThisMode().
This function is used internally by widgets that support TQWidget::customWhatsThis(); applications do not usually call it. An example of such a widget is TQPopupMenu: menus still work normally in "What's this?" mode but also provide help texts for individual menu items.
@ -74,7 +74,7 @@ See also QMouseEvent, TQWidget::grabMouse(), and Event Classes.
.SH "QWheelEvent::QWheelEvent ( const TQPoint & pos, int delta, int state, Orientation orient = Vertical )"
Constructs a wheel event object.
.PP
The globalPos() is initialized to QCursor::pos(), i.e. \fIpos\fR, which is usually (but not always) right. Use the other constructor if you need to specify the global position explicitly. \fIdelta\fR contains the rotation distance, \fIstate\fR holds the keyboard modifier flags at the time of the event and \fIorient\fR holds the wheel's orientation.
The globalPos() is initialized to TQCursor::pos(), i.e. \fIpos\fR, which is usually (but not always) right. Use the other constructor if you need to specify the global position explicitly. \fIdelta\fR contains the rotation distance, \fIstate\fR holds the keyboard modifier flags at the time of the event and \fIorient\fR holds the wheel's orientation.
.PP
See also pos(), delta(), and state().
.SH "QWheelEvent::QWheelEvent ( const TQPoint & pos, const TQPoint & globalPos, int delta, int state, Orientation orient = Vertical )"
@ -94,7 +94,7 @@ Returns the distance that the wheel is rotated expressed in multiples or divisio
.PP
The \fIwheel delta\fR constant was defined to be 120 by wheel mouse vendors to allow building finer-resolution wheels in the future, including perhaps a freely rotating wheel with no notches. The expectation is that such a device would send more messages per rotation but with a smaller value in each message.
Returns the global position of the mouse pointer \fIat the time of the event\fR. This is important on asynchronous window systems such as X11; whenever you move your widgets around in response to mouse events, globalPos() can differ a lot from the current pointer position QCursor::pos().
Returns the global position of the mouse pointer \fIat the time of the event\fR. This is important on asynchronous window systems such as X11; whenever you move your widgets around in response to mouse events, globalPos() can differ a lot from the current pointer position TQCursor::pos().
.BI "virtual void \fBcloseEvent\fR ( QCloseEvent * e )"
.BI "virtual void \fBcloseEvent\fR ( TQCloseEvent * e )"
.br
.ti -1c
.BI "virtual void \fBcontextMenuEvent\fR ( QContextMenuEvent * e )"
.BI "virtual void \fBcontextMenuEvent\fR ( TQContextMenuEvent * e )"
.br
.ti -1c
.BI "virtual void \fBimStartEvent\fR ( QIMEvent * e )"
@ -1227,7 +1227,7 @@ The repaint() function calls this function if necessary, so in general you do no
.SH "bool TQWidget::close ()\fC [slot]\fR"
Closes this widget. Returns TRUE if the widget was closed; otherwise returns FALSE.
.PP
First it sends the widget a QCloseEvent. The widget is hidden if it accepts the close event. The default implementation of TQWidget::closeEvent() accepts the close event.
First it sends the widget a TQCloseEvent. The widget is hidden if it accepts the close event. The default implementation of TQWidget::closeEvent() accepts the close event.
.PP
The QApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.
.PP
@ -1238,19 +1238,19 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
Closes this widget. Returns TRUE if the widget was closed; otherwise returns FALSE.
.PP
If \fIalsoDelete\fR is TRUE or the widget has the WDestructiveClose widget flag, the widget is also deleted. The widget can prevent itself from being closed by rejecting the QCloseEvent it gets. A close events is delivered to the widget no matter if the widget is visible or not.
If \fIalsoDelete\fR is TRUE or the widget has the WDestructiveClose widget flag, the widget is also deleted. The widget can prevent itself from being closed by rejecting the TQCloseEvent it gets. A close events is delivered to the widget no matter if the widget is visible or not.
.PP
The QApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.
.PP
Note that closing the QApplication::mainWidget() terminates the application.
.PP
See also closeEvent(), QCloseEvent, hide(), QApplication::quit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
.SH "void TQWidget::closeEvent ( QCloseEvent * e )\fC [virtual protected]\fR"
See also closeEvent(), TQCloseEvent, hide(), QApplication::quit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
.SH "void TQWidget::closeEvent ( TQCloseEvent * e )\fC [virtual protected]\fR"
This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive widget close events.
.PP
The default implementation calls e->accept(), which hides this widget. See the QCloseEvent documentation for more details.
The default implementation calls e->accept(), which hides this widget. See the TQCloseEvent documentation for more details.
.PP
See also event(), hide(), close(), and QCloseEvent.
See also event(), hide(), close(), and TQCloseEvent.
.PP
Examples:
.)l action/application.cpp, application/application.cpp, chart/chartform.cpp, i18n/mywidget.cpp, mdi/application.cpp, popup/popup.cpp, and qwerty/qwerty.cpp.
@ -1264,12 +1264,12 @@ Call constPolish() from functions like sizeHint() that depends on the widget bei
\fBWarning:\fR Do not call constPolish() on a widget from inside that widget's constructor.
.PP
See also polish().
.SH "void TQWidget::contextMenuEvent ( QContextMenuEvent * e )\fC [virtual protected]\fR"
.SH "void TQWidget::contextMenuEvent ( TQContextMenuEvent * e )\fC [virtual protected]\fR"
This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive widget context menu events.
.PP
The default implementation calls e->ignore(), which rejects the context event. See the QContextMenuEvent documentation for more details.
The default implementation calls e->ignore(), which rejects the context event. See the TQContextMenuEvent documentation for more details.
@ -1280,7 +1280,7 @@ Initializes the window (sets the geometry etc.) if \fIinitializeWindow\fR is TRU
Destroys the old window if \fIdestroyOldWindow\fR is TRUE. If \fIdestroyOldWindow\fR is FALSE, you are responsible for destroying the window yourself (using platform native code).
.PP
The TQWidget constructor calls create(0,TRUE,TRUE) to create a window for this widget.
.SH "const QCursor & TQWidget::cursor () const"
.SH "const TQCursor & TQWidget::cursor () const"
Returns the cursor shape for this widget. See the "cursor" property for details.