<trbgcolor=#f0f0f0><td><b><ahref="qlistviewitem.html">TQListViewItem</a></b><td>Implements a list view item
<trbgcolor=#f0f0f0><td><b><ahref="qlistviewitemiterator.html">TQListViewItemIterator</a></b><td>Iterator for collections of TQListViewItems
<trbgcolor=#f0f0f0><td><b><ahref="tqlocalfs.html">TQLocalFs</a></b><td>Implementation of a TQNetworkProtocol that works on the local file system
<trbgcolor=#f0f0f0><td><b><ahref="ntqlocale.html">TQLocale</a></b><td>Converts between numbers and their string representations in various languages
<trbgcolor=#f0f0f0><td><b><ahref="tqlocale.html">TQLocale</a></b><td>Converts between numbers and their string representations in various languages
<trbgcolor=#f0f0f0><td><b><ahref="tqmacmime.html">TQMacMime</a></b><td>Maps open-standard MIME to Mac flavors
<trbgcolor=#f0f0f0><td><b><ahref="qmacstyle.html">TQMacStyle</a></b><td>Implements an Appearance Manager style
<trbgcolor=#f0f0f0><td><b><ahref="tqmainwindow.html">TQMainWindow</a></b><td>Main application window, with a menu bar, dock windows (e.g. for toolbars), and a status bar
<trbgcolor=#f0f0f0><td><b><ahref="ntqvariant.html">TQVariant</a></b><td>Acts like a union for the most common TQt data types
<trbgcolor=#f0f0f0><td><b><ahref="tqwmatrix.html">TQWMatrix</a></b><td>2D transformations of a coordinate system
<trbgcolor=#f0f0f0><td><b><ahref="tqwaitcondition.html">TQWaitCondition</a></b><td>Allows waiting/waking for conditions between threads
<trbgcolor=#f0f0f0><td><b><ahref="ntqwhatsthis.html">TQWhatsThis</a></b><td>Simple description of any widget, i.e. answering the question "What's this?"
<trbgcolor=#f0f0f0><td><b><ahref="tqwhatsthis.html">TQWhatsThis</a></b><td>Simple description of any widget, i.e. answering the question "What's this?"
<trbgcolor=#f0f0f0><td><b><ahref="qwheelevent.html">TQWheelEvent</a></b><td>Parameters that describe a wheel event
<trbgcolor=#f0f0f0><td><b><ahref="tqwidget.html">TQWidget</a></b><td>The base class of all user interface objects
<trbgcolor=#f0f0f0><td><b><ahref="tqwidgetfactory.html">TQWidgetFactory</a></b><td>For the dynamic creation of widgets from TQt Designer .ui files
<trbgcolor=#f0f0f0><td><b><ahref="ntqsyntaxhighlighter.html">TQSyntaxHighlighter</a></b><td>Base class for implementing TQTextEdit syntax highlighters
<trbgcolor=#f0f0f0><td><b><ahref="tqsyntaxhighlighter.html">TQSyntaxHighlighter</a></b><td>Base class for implementing TQTextEdit syntax highlighters
<trbgcolor=#f0f0f0><td><b><ahref="tqtextedit.html">TQTextEdit</a></b><td>Powerful single-page rich text editor
<trbgcolor=#f0f0f0><td><b><ahref="tqtoolbutton.html">TQToolButton</a></b><td>Quick-access button to commands or options, usually used inside a TQToolBar
<p>Now we need to relate each of the text labels to the corresponding widget. We do this by creating "buddies".</p>
<p>A widget that does not accept focus itself, e.g. a <ahref="ntqlabel.html">TQLabel</a>, can have an accelerator that will pass the focus to its "buddy", e.g. a <ahref="ntqlineedit.html">TQLineEdit</a>. In <em>TQt Designer</em>, we enable this by setting the first widget's <em>buddy</em> property to the name of the buddy widget.</p>
<p>A widget that does not accept focus itself, e.g. a <ahref="tqlabel.html">TQLabel</a>, can have an accelerator that will pass the focus to its "buddy", e.g. a <ahref="ntqlineedit.html">TQLineEdit</a>. In <em>TQt Designer</em>, we enable this by setting the first widget's <em>buddy</em> property to the name of the buddy widget.</p>
<ul><li><p>Click the <b>Set Buddy</b> toolbar button (or press <b>F12</b>). Click the Enter Number label, drag the line to the numberLineEdit, then release.</p>
<li><p>Click the <b>Set Buddy</b> toolbar button. Click the Convert From label, drag the line to the fromComboBox, then release.</p>
<li><p>Click the <b>Set Buddy</b> toolbar button. Click the Convert To label, drag the line to the toComboBox, then release.</p>
<p>We can use one of TQt's static dialogs to get the user to choose a color, but we need our own dialog to get them to give it a name. We'll create that dialog now.</p>
<p>Click <b>File|New</b> to invoke the <em>New File</em> dialog, then click "Dialog", then click <b>OK</b>. Drag a corner of the new form to make it a lot smaller. Change the form's name (in the <ahref="designer-manual-3.html#using-the-property-editor-sidebar">Property Editor</a>) to "ColorNameForm", and change its caption to "Color Tool -- Color Name". Click <b>File|Save</b>, then click <b>Save</b> to save it.</p>
<p>We'll now add some widgets to the dialog. Don't worry about precise positioning or sizing; we'll get <em>TQt Designer</em> to lay the form out perfectly for us shortly.</p>
<p>We need to create a <ahref="ntqlabel.html">TQLabel</a> that will show the color the user has chosen. Click the TextLabel tool in the Toolbox, then click on the left hand side of the form. Change the label's <em>name</em> property to "colorLabel", and delete the text in the <em>text</em> property. Click the <em>pixmap</em> property's ellipsis button and choose the "editraise.png" image. Change the <em>minimumSize</em> property's <em>width</em> sub-property to 80, and set the <em>scaledContents</em> property to True.</p>
<p>Click the TextLabel tool again, then click to the right of the colorLabel, towards the top of the form. Change the <em>text</em> property to "&Name". Note that the ampersand is displayed; this is because a <ahref="ntqlabel.html">TQLabel</a> cannot accept focus and we haven't specified a focus widget ("buddy") yet.</p>
<p>We need to create a <ahref="tqlabel.html">TQLabel</a> that will show the color the user has chosen. Click the TextLabel tool in the Toolbox, then click on the left hand side of the form. Change the label's <em>name</em> property to "colorLabel", and delete the text in the <em>text</em> property. Click the <em>pixmap</em> property's ellipsis button and choose the "editraise.png" image. Change the <em>minimumSize</em> property's <em>width</em> sub-property to 80, and set the <em>scaledContents</em> property to True.</p>
<p>Click the TextLabel tool again, then click to the right of the colorLabel, towards the top of the form. Change the <em>text</em> property to "&Name". Note that the ampersand is displayed; this is because a <ahref="tqlabel.html">TQLabel</a> cannot accept focus and we haven't specified a focus widget ("buddy") yet.</p>
<p>Click the LineEdit tool, then click to the right of the "Name" label, again towards the top of the form. Change the <em>name</em> property to "colorLineEdit".</p>
<p>Click on the "Name" label and change its <em>buddy</em> property to "colorLineEdit". The ampersand has now disappeared and <b>Alt+N</b> will set the focus in the colorLineEdit.</p>
<p>Click the PushButton tool, then click below the "colorLabel". Change the button's <em>name</em> property to "okPushButton", its <em>text</em> property to "OK", and its <em>default</em> property to True.</p>
<p>The ColorNameForm dialog will be called from the main form. The caller will firstly call one of TQt's static "choose a color" dialogs, and if the user chooses a color, will then invoke our custom dialog. Since we're going to use a "choose a color" dialog we will need the appropriate header file. We'll also be accessing the dialog's colorLabel (to set it to the chosen color), and the dialog's line edit (to retrieve the color name), so we'll need appropriate headers for these too.</p>
<p>Click "MainForm" in the Project Overview window so that Object Explorer shows the main form's objects.</p>
<p>Click Object Explorer's Members tab. Right click "Includes (in Implementation)", then click <b>Edit</b> to invoke the <em>Edit Includes (in Implementation)</em> dialog. Click <b>Add</b> then enter "tqcolordialog.h". Click <b>Add</b> again, and enter "ntqlabel.h". Similarly add "ntqlineedit.h". We also need to include the header for the form we've just created, so add "colornameform.h", and since it is our last entry press <b>Enter</b>, then click <b>Close</b>.</p>
<p>Click Object Explorer's Members tab. Right click "Includes (in Implementation)", then click <b>Edit</b> to invoke the <em>Edit Includes (in Implementation)</em> dialog. Click <b>Add</b> then enter "tqcolordialog.h". Click <b>Add</b> again, and enter "tqlabel.h". Similarly add "ntqlineedit.h". We also need to include the header for the form we've just created, so add "colornameform.h", and since it is our last entry press <b>Enter</b>, then click <b>Close</b>.</p>
<p>You should now have added the following declarations to your includes (in implementation):</p>
<ul><li><p>"tqcolordialog.h"</p>
<li><p>"ntqlabel.h"</p>
<li><p>"tqlabel.h"</p>
<li><p>"ntqlineedit.h"</p>
<li><p>"colornameform.h"</p>
</ul><p>Now we're ready to enter the <tt>editAdd()</tt> slot's code. Click "mainform.ui.h" in the Project Overview to invoke the code editor.</p>
<p>Although Glade does not target TQt, the layout system and the widget set of GTK+ are similar to those of TQt, so the filter will retain most of the information in the<!-- index .glade --><tt>.glade</tt> file.</p>
<p>There are some considerations regarding the conversion of Glade files, as listed below:</p>
<ul><li><p>Ampersands (&) in labels</p>
<p>TQt displays an ampersand when a <ahref="ntqlabel.html">TQLabel</a> has no buddy. (A buddy is a widget that accepts focus on behalf of a <ahref="ntqlabel.html">TQLabel</a>.) Glade allows GtkLabel widgets with an (underlined) accelerator key but with no buddy. This is an error since users expect underlined characters to be accelerators. In this situation, TQt displays the ampersand itself instead of underlining the accelerator key. You should go over these <ahref="ntqlabel.html">TQLabel</a> widgets and set their "<em>buddy</em>" property.</p>
<p>TQt displays an ampersand when a <ahref="tqlabel.html">TQLabel</a> has no buddy. (A buddy is a widget that accepts focus on behalf of a <ahref="tqlabel.html">TQLabel</a>.) Glade allows GtkLabel widgets with an (underlined) accelerator key but with no buddy. This is an error since users expect underlined characters to be accelerators. In this situation, TQt displays the ampersand itself instead of underlining the accelerator key. You should go over these <ahref="tqlabel.html">TQLabel</a> widgets and set their "<em>buddy</em>" property.</p>
<li><p>Layout placeholders</p>
<p>GTK allows a layout position to be occupied by a placeholder. <em>TQt Designer</em> converts those placeholders into <ahref="ntqlabel.html">TQLabel</a>s whose text is "?" in red, so that you can find them and fix them manually.</p>
<p>GTK allows a layout position to be occupied by a placeholder. <em>TQt Designer</em> converts those placeholders into <ahref="tqlabel.html">TQLabel</a>s whose text is "?" in red, so that you can find them and fix them manually.</p>
<li><p>GTK+ or GNOME widget with no TQt equivalent</p>
<p>TQt has equivalents for most GTK+ widgets, but Glade also supports GNOME, whose goal is to provide a complete desktop environment. Because TQt's scope is narrower, when <em>TQt Designer</em> encounters a widget it cannot convert, it replaces it with a label that indicates the problem. For example, a GnomePaperSelector will be replaced by a <ahref="ntqlabel.html">TQLabel</a> whose text is "GnomePaperSelector?" in red. If you are porting to KDE, you might want to use the corresponding KDE widget.</p>
<p>TQt has equivalents for most GTK+ widgets, but Glade also supports GNOME, whose goal is to provide a complete desktop environment. Because TQt's scope is narrower, when <em>TQt Designer</em> encounters a widget it cannot convert, it replaces it with a label that indicates the problem. For example, a GnomePaperSelector will be replaced by a <ahref="tqlabel.html">TQLabel</a> whose text is "GnomePaperSelector?" in red. If you are porting to KDE, you might want to use the corresponding KDE widget.</p>
<p>Other GTK+/GNOME widgets are only supported in certain contexts. For example, the GnomeDruid can be embedded in another widget, whereas the corresponding <ahref="ntqwizard.html">TQWizard</a> class cannot.</p>
<li><p>Message boxes and other high-level dialogs</p>
<p>Glade supports editing of GnomeMessageBox, GtkFileSelection, GtkFontSelectionDialog and others. This is trivially achieved in TQt by means of a <ahref="ntqmessagebox.html">TQMessageBox</a> dialog, a <ahref="tqfiledialog.html">TQFileDialog</a>, a <ahref="tqfontdialog.html">TQFontDialog</a>, etc., in C++ code.</p>
<aname="1-3"></a><p> It's not unusual for keyboard shortcuts to move the focus. This can
happen implicitly by opening modal dialogs, but also explicitly using
focus accelerators such as those provided by <ahref="ntqlabel.html#setBuddy">TQLabel::setBuddy</a>(), <ahref="ntqgroupbox.html">TQGroupBox</a> and <ahref="ntqtabbar.html">TQTabBar</a>.
focus accelerators such as those provided by <ahref="tqlabel.html#setBuddy">TQLabel::setBuddy</a>(), <ahref="ntqgroupbox.html">TQGroupBox</a> and <ahref="ntqtabbar.html">TQTabBar</a>.
<p> We advise supporting shortcut focus for all widgets that the user may
want to jump to. For example, a tab dialog can have keyboard shortcuts
for each of its pages, so the user can press e.g. Alt+P to step to the
@ -53,7 +53,7 @@ help is a digression from their real task.
<trbgcolor=#f0f0f0><td><b><ahref="tqtextbrowser.html">TQTextBrowser</a></b><td>Rich text browser with hypertext navigation
<trbgcolor=#f0f0f0><td><b><ahref="tqtooltip.html">TQToolTip</a></b><td>Tool tips (balloon help) for any widget or rectangular part of a widget
<trbgcolor=#f0f0f0><td><b><ahref="tqtooltipgroup.html">TQToolTipGroup</a></b><td>Collects tool tips into related groups
<trbgcolor=#f0f0f0><td><b><ahref="ntqwhatsthis.html">TQWhatsThis</a></b><td>Simple description of any widget, i.e. answering the question "What's this?"
<trbgcolor=#f0f0f0><td><b><ahref="tqwhatsthis.html">TQWhatsThis</a></b><td>Simple description of any widget, i.e. answering the question "What's this?"
<!-- index TQ_OBJECT --><!-- index PrintPanel!in Translation Tutorial --><p>PrintPanel is a <ahref="tqwidget.html">TQWidget</a>. It needs the <tt>TQ_OBJECT</tt> macro for <tt>tr()</tt> to work properly.</p>
<p>The implementation file is <tt>printpanel.cpp</tt>.</p>
<pre> /*
<ahref="ntqlabel.html">TQLabel</a> *lab = new <ahref="ntqlabel.html">TQLabel</a>( <ahref="tqobject.html#tr">tr</a>("<b>TROLL PRINT</b>"), this );
<ahref="tqlabel.html">TQLabel</a> *lab = new <ahref="tqlabel.html">TQLabel</a>( <ahref="tqobject.html#tr">tr</a>("<b>TROLL PRINT</b>"), this );
<!-- index Troll Print --><p>Some of the code is commented out in Troll Print 1.0; you will uncomment it later, for Troll Print 1.1.</p>
@ -518,7 +518,7 @@ TRANSLATIONS = tt3_pt.ts
</pre>
<h5><aname="2-3-3"></a>Troll Print 1.1</h5>
<p>We'll now prepare release 1.1 of Troll Print. Start your favorite text editor and follow these steps:</p>
<ul><li><p>Uncomment the two lines that create a <ahref="ntqlabel.html">TQLabel</a> with the text "<b>TROLL PRINT</b>" in <tt>printpanel.cpp</tt>.</p>
<ul><li><p>Uncomment the two lines that create a <ahref="tqlabel.html">TQLabel</a> with the text "<b>TROLL PRINT</b>" in <tt>printpanel.cpp</tt>.</p>
<li><p>Word-tidying: Replace "2-sided" by "Two-sided" in <tt>printpanel.cpp</tt>.</p>
<li><p>Replace "1.0" with "1.1" everywhere it occurs in <tt>mainwindow.cpp</tt>.</p>
<li><p>Update the copyright year to 1999-2000 in <tt>mainwindow.cpp</tt>.</p>
@ -282,7 +282,7 @@ Sets a What's This help text for the accelerator item <em>id</em> to <em>text</e
and the user hits the accelerator key.
<p> To set What's This help on a menu item (with or without an
accelerator key), use <ahref="tqmenudata.html#setWhatsThis">TQMenuData::setWhatsThis</a>().
<p><p>See also <ahref="#whatsThis">whatsThis</a>(), <ahref="ntqwhatsthis.html#inWhatsThisMode">TQWhatsThis::inWhatsThisMode</a>(), <ahref="tqmenudata.html#setWhatsThis">TQMenuData::setWhatsThis</a>(), and <ahref="tqaction.html#whatsThis-prop">TQAction::whatsThis</a>.
<p><p>See also <ahref="#whatsThis">whatsThis</a>(), <ahref="tqwhatsthis.html#inWhatsThisMode">TQWhatsThis::inWhatsThisMode</a>(), <ahref="tqmenudata.html#setWhatsThis">TQMenuData::setWhatsThis</a>(), and <ahref="tqaction.html#whatsThis-prop">TQAction::whatsThis</a>.
ValueChange when the position of a slider has been changed. <em>control</em> is the ID of the child element that has changed. When <em>control</em> is 0, the object itself has changed.
<p> Call this function whenever the state of your accessible object or
one of it's sub-elements has been changed either programmatically
(e.g. by calling <ahref="ntqlabel.html#setText">TQLabel::setText</a>()) or by user interaction.
(e.g. by calling <ahref="tqlabel.html#setText">TQLabel::setText</a>()) or by user interaction.
<p> If there are no accessibility tools listening to this event, the
performance penalty for calling this function is minor, but if determining
the parameters of the call is expensive you can use <ahref="#isActive">isActive</a>() to
@ -197,7 +197,7 @@ inside the frame. It should only draw inside <a href="#contentsRect">contentsRec
default function does nothing.
<p><p>See also <ahref="#contentsRect-prop">contentsRect</a> and <ahref="tqpainter.html#setClipRect">TQPainter::setClipRect</a>().
<p>Reimplemented in <ahref="ntqlabel.html#drawContents">TQLabel</a>, <ahref="ntqlcdnumber.html#drawContents">TQLCDNumber</a>, <ahref="tqmenubar.html#drawContents">TQMenuBar</a>, and <ahref="tqpopupmenu.html#drawContents">TQPopupMenu</a>.
<p>Reimplemented in <ahref="tqlabel.html#drawContents">TQLabel</a>, <ahref="ntqlcdnumber.html#drawContents">TQLCDNumber</a>, <ahref="tqmenubar.html#drawContents">TQMenuBar</a>, and <ahref="tqpopupmenu.html#drawContents">TQPopupMenu</a>.
@ -79,7 +79,7 @@ also be used as a separate widget.
<p>
<p> The screenshot below shows a <ahref="ntqtabdialog.html">TQTabDialog</a>. The tabs (<ahref="ntqtabbar.html">TQTabBar</a>) or the
more convenient class <ahref="ntqtabwidget.html">TQTabWidget</a>, which combines a tab bar with
the pages, can be used separately. In the visible page you see a <ahref="ntqlabel.html">TQLabel</a>, the range controls <ahref="ntqslider.html">TQSlider</a> and <ahref="ntqspinbox.html">TQSpinBox</a> and below a <ahref="ntqlcdnumber.html">TQLCDNumber</a>. In the bottom row there are some <ahref="ntqpushbutton.html">TQPushButton</a>s.
the pages, can be used separately. In the visible page you see a <ahref="tqlabel.html">TQLabel</a>, the range controls <ahref="ntqslider.html">TQSlider</a> and <ahref="ntqspinbox.html">TQSpinBox</a> and below a <ahref="ntqlcdnumber.html">TQLCDNumber</a>. In the bottom row there are some <ahref="ntqpushbutton.html">TQPushButton</a>s.
<p><center><imgsrc="qtabdlg-w.png"></center>
<p> In the screenshot below there's a <ahref="tqtextbrowser.html">TQTextBrowser</a> displaying a HTML
page. See also <ahref="tqtextedit.html">TQTextEdit</a>.
<li><ahref="tqfontdatabase.html#smoothSizes">TQFontDatabase::smoothSizes</a>( const TQString & family, const TQString & style, const TQString & )
<li><ahref="tqfontdatabase.html#styles">TQFontDatabase::styles</a>( const TQString & family, const TQString & ) const
<li><ahref="tqfontdatabase.html#weight">TQFontDatabase::weight</a>( const TQString & family, const TQString & style, const TQString & ) const
<li><ahref="tqstyle.html#tabbarMetrics">TQStyle::tabbarMetrics</a>( const <ahref="tqwidget.html">TQWidget</a> *t, int & hf, int & vf, int & ov ) const
action. The text may contain rich text (HTML-like tags -- see
<a href="tqstylesheet.html">TQStyleSheet</a> for the list of supported tags). There is no default
"What's This" text.
<p> <p>See also <a href="ntqwhatsthis.html">QWhatsThis</a>.
<p> <p>See also <a href="tqwhatsthis.html">TQWhatsThis</a>.
<p>Set this property's value with <a href="tqaction.html#setWhatsThis">setWhatsThis</a>() and get this property's value with <a href="tqaction.html#whatsThis">whatsThis</a>().
</doc>
@ -1834,29 +1834,29 @@ of 0.
</doc>
</property>
<property>
<name>QLabel::alignment</name>
<doc href="ntqlabel.html#alignment-prop">
<name>TQLabel::alignment</name>
<doc href="tqlabel.html#alignment-prop">
<p>This property holds the alignment of the label's contents.
<p>The alignment is a bitwise OR of <a href="ntqt.html#AlignmentFlags-enum">TQt::AlignmentFlags</a> and <a href="ntqt.html#TextFlags-enum">TQt::TextFlags</a> values. The <a href="ntqt.html#TextFlags-enum">ExpandTabs</a>, <a href="ntqt.html#TextFlags-enum">SingleLine</a> and <a href="ntqt.html#TextFlags-enum">ShowPrefix</a> flags apply only if the label contains plain text;
otherwise they are ignored. The <a href="ntqt.html#TextFlags-enum">DontClip</a> flag is always
ignored. <a href="ntqt.html#TextFlags-enum">WordBreak</a> applies to both rich text and plain text
labels. The <a href="ntqt.html#TextFlags-enum">BreakAnywhere</a> flag is not supported in QLabel.
labels. The <a href="ntqt.html#TextFlags-enum">BreakAnywhere</a> flag is not supported in TQLabel.
<p> If the label has a buddy, the <a href="ntqt.html#TextFlags-enum">ShowPrefix</a> flag is forced to
TRUE.
<p> The default alignment is <tt>AlignAuto | AlignVCenter | ExpandTabs</tt>
if the label doesn't have a buddy and <tt>AlignAuto | AlignVCenter | ExpandTabs | ShowPrefix</tt> if the label has a buddy. If the label
contains rich text, additionally <a href="ntqt.html#TextFlags-enum">WordBreak</a> is turned on.
<p> <p>See also <a href="ntqt.html#AlignmentFlags-enum">TQt::AlignmentFlags</a>, <a href="ntqlabel.html#setBuddy">setBuddy</a>(), and <a href="ntqlabel.html#text-prop">text</a>.
<p> <p>See also <a href="ntqt.html#AlignmentFlags-enum">TQt::AlignmentFlags</a>, <a href="tqlabel.html#setBuddy">setBuddy</a>(), and <a href="tqlabel.html#text-prop">text</a>.
<p>Set this property's value with <a href="ntqlabel.html#setAlignment">setAlignment</a>() and get this property's value with <a href="ntqlabel.html#alignment">alignment</a>().
<p>Set this property's value with <a href="tqlabel.html#setAlignment">setAlignment</a>() and get this property's value with <a href="tqlabel.html#alignment">alignment</a>().
</doc>
</property>
<property>
<name>QLabel::indent</name>
<doc href="ntqlabel.html#indent-prop">
<name>TQLabel::indent</name>
<doc href="tqlabel.html#indent-prop">
<p>This property holds the label's text indent in pixels.
<p>If a label displays text, the indent applies to the left edge if
<a href="ntqlabel.html#alignment">alignment</a>() is <a href="ntqt.html#AlignmentFlags-enum">AlignLeft</a>, to the right edge if alignment() is
<a href="tqlabel.html#alignment">alignment</a>() is <a href="ntqt.html#AlignmentFlags-enum">AlignLeft</a>, to the right edge if alignment() is
<a href="ntqt.html#AlignmentFlags-enum">AlignRight</a>, to the top edge if alignment() is <a href="ntqt.html#AlignmentFlags-enum">AlignTop</a>, and
to to the bottom edge if alignment() is <a href="ntqt.html#AlignmentFlags-enum">AlignBottom</a>.
<p> If indent is negative, or if no indent has been set, the label
@ -1864,69 +1864,69 @@ computes the effective indent as follows: If <a href="ntqframe.html#frameWidt
the effective indent becomes 0. If frameWidth() is greater than 0,
the effective indent becomes half the width of the "x" character
of the widget's current <a href="tqwidget.html#font">font</a>().
<p> <p>See also <a href="ntqlabel.html#alignment-prop">alignment</a>, <a href="ntqframe.html#frameWidth-prop">frameWidth</a>, and <a href="tqwidget.html#font-prop">font</a>.
<p> <p>See also <a href="tqlabel.html#alignment-prop">alignment</a>, <a href="ntqframe.html#frameWidth-prop">frameWidth</a>, and <a href="tqwidget.html#font-prop">font</a>.
<p>Set this property's value with <a href="ntqlabel.html#setIndent">setIndent</a>() and get this property's value with <a href="ntqlabel.html#indent">indent</a>().
<p>Set this property's value with <a href="tqlabel.html#setIndent">setIndent</a>() and get this property's value with <a href="tqlabel.html#indent">indent</a>().
</doc>
</property>
<property>
<name>QLabel::pixmap</name>
<doc href="ntqlabel.html#pixmap-prop">
<name>TQLabel::pixmap</name>
<doc href="tqlabel.html#pixmap-prop">
<p>This property holds the label's pixmap.
<p>If no pixmap has been set this will return an invalid pixmap.
<p> Setting the pixmap clears any previous content, and resizes the
label if <a href="ntqlabel.html#autoResize">QLabel::autoResize</a>() is TRUE. The buddy accelerator,
label if <a href="tqlabel.html#autoResize">TQLabel::autoResize</a>() is TRUE. The buddy accelerator,
if any, is disabled.
<p>Set this property's value with <a href="ntqlabel.html#setPixmap">setPixmap</a>() and get this property's value with <a href="ntqlabel.html#pixmap">pixmap</a>().
<p>Set this property's value with <a href="tqlabel.html#setPixmap">setPixmap</a>() and get this property's value with <a href="tqlabel.html#pixmap">pixmap</a>().
</doc>
</property>
<property>
<name>QLabel::scaledContents</name>
<doc href="ntqlabel.html#scaledContents-prop">
<name>TQLabel::scaledContents</name>
<doc href="tqlabel.html#scaledContents-prop">
<p>This property holds whether the label will scale its contents to fill all available space.
<p>When enabled and the label shows a pixmap, it will scale the
pixmap to fill the available space.
<p> This property's default is FALSE.
<p> <p>See also <a href="ntqlabel.html#scaledContents-prop">scaledContents</a>.
<p> <p>See also <a href="tqlabel.html#scaledContents-prop">scaledContents</a>.
<p>Set this property's value with <a href="ntqlabel.html#setScaledContents">setScaledContents</a>() and get this property's value with <a href="ntqlabel.html#hasScaledContents">hasScaledContents</a>().
<p>Set this property's value with <a href="tqlabel.html#setScaledContents">setScaledContents</a>() and get this property's value with <a href="tqlabel.html#hasScaledContents">hasScaledContents</a>().
</doc>
</property>
<property>
<name>QLabel::text</name>
<doc href="ntqlabel.html#text-prop">
<name>TQLabel::text</name>
<doc href="tqlabel.html#text-prop">
<p>This property holds the label's text.
<p>If no text has been set this will return an empty string. Setting
the text clears any previous content, unless they are the same.
<p> The text will be interpreted either as a plain text or as a rich
text, depending on the text format setting; see <a href="ntqlabel.html#setTextFormat">setTextFormat</a>().
The default setting is <a href="ntqt.html#TextFormat-enum">AutoText</a>, i.e. QLabel will try to
text, depending on the text format setting; see <a href="tqlabel.html#setTextFormat">setTextFormat</a>().
The default setting is <a href="ntqt.html#TextFormat-enum">AutoText</a>, i.e. TQLabel will try to
auto-detect the format of the text set.
<p> If the text is interpreted as a plain text and a buddy has been
set, the buddy accelerator key is updated from the new text.
<p> The label resizes itself if auto-resizing is enabled.
<p> Note that Qlabel is well-suited to display small rich text
<p> Note that TQLabel is well-suited to display small rich text
documents, i.e. those small documents that get their document
specific settings (font, text color, link color) from the label's
palette and font properties. For large documents, use <a href="tqtextedit.html">TQTextEdit</a>
in read-only mode instead. TQTextEdit will flicker less on resize
and can also provide a scrollbar when necessary.
<p> <p>See also <a href="ntqlabel.html#textFormat-prop">textFormat</a>, <a href="ntqlabel.html#setBuddy">setBuddy</a>(), and <a href="ntqlabel.html#alignment-prop">alignment</a>.
<p> <p>See also <a href="tqlabel.html#textFormat-prop">textFormat</a>, <a href="tqlabel.html#setBuddy">setBuddy</a>(), and <a href="tqlabel.html#alignment-prop">alignment</a>.
<p>Set this property's value with <a href="ntqlabel.html#setText">setText</a>() and get this property's value with <a href="ntqlabel.html#text">text</a>().
<p>Set this property's value with <a href="tqlabel.html#setText">setText</a>() and get this property's value with <a href="tqlabel.html#text">text</a>().
</doc>
</property>
<property>
<name>QLabel::textFormat</name>
<doc href="ntqlabel.html#textFormat-prop">
<name>TQLabel::textFormat</name>
<doc href="tqlabel.html#textFormat-prop">
<p>This property holds the label's text format.
<p>See the <a href="ntqt.html#TextFormat-enum">TQt::TextFormat</a> enum for an explanation of the possible
options.
<p> The default format is <a href="ntqt.html#TextFormat-enum">AutoText</a>.
<p> <p>See also <a href="ntqlabel.html#text-prop">text</a>.
<p> <p>See also <a href="tqlabel.html#text-prop">text</a>.
<p>Set this property's value with <a href="ntqlabel.html#setTextFormat">setTextFormat</a>() and get this property's value with <a href="ntqlabel.html#textFormat">textFormat</a>().
<p>Set this property's value with <a href="tqlabel.html#setTextFormat">setTextFormat</a>() and get this property's value with <a href="tqlabel.html#textFormat">textFormat</a>().
</doc>
</property>
<property>
@ -4414,12 +4414,12 @@ on top-level widgets.
which means the widget will not receive any events in Whats This
mode.
<p> The widget may leave What's This mode by calling
<a href="ntqwhatsthis.html#leaveWhatsThisMode">QWhatsThis::leaveWhatsThisMode</a>(), with or without actually
<a href="tqwhatsthis.html#leaveWhatsThisMode">TQWhatsThis::leaveWhatsThisMode</a>(), with or without actually
displaying any help text.
<p> You can also reimplement customWhatsThis() if your widget is a
"passive interactor" supposed to work under all circumstances.
Simply don't call QWhatsThis::leaveWhatsThisMode() in that case.
<p> <p>See also <a href="ntqwhatsthis.html#inWhatsThisMode">QWhatsThis::inWhatsThisMode</a>() and <a href="ntqwhatsthis.html#leaveWhatsThisMode">QWhatsThis::leaveWhatsThisMode</a>().
Simply don't call TQWhatsThis::leaveWhatsThisMode() in that case.
<p> <p>See also <a href="tqwhatsthis.html#inWhatsThisMode">TQWhatsThis::inWhatsThisMode</a>() and <a href="tqwhatsthis.html#leaveWhatsThisMode">TQWhatsThis::leaveWhatsThisMode</a>().
<p>Get this property's value with <a href="tqwidget.html#customWhatsThis">customWhatsThis</a>().
<ahref="ntqlabel.html">TQLabel</a> *label1 = new <ahref="ntqlabel.html">TQLabel</a>( TQString( "Enter a value between\n%1 and %2:" ).arg( -INT_MAX ).arg( INT_MAX ), cell2 );
<ahref="tqlabel.html">TQLabel</a> *label1 = new <ahref="tqlabel.html">TQLabel</a>( TQString( "Enter a value between\n%1 and %2:" ).arg( -INT_MAX ).arg( INT_MAX ), cell2 );
<p> This walkthrough shows simple use of <ahref="tqmainwindow.html">TQMainWindow</a>, <ahref="tqmenubar.html">TQMenuBar</a>, <ahref="tqpopupmenu.html">TQPopupMenu</a>, <ahref="tqtoolbar.html">TQToolBar</a> and <ahref="tqstatusbar.html">TQStatusBar</a> - classes that every
modern application window tends to use. (See also <ahref="tutorial2.html">Tutorial #2</a>.)
<p> It also illustrates some aspects of <ahref="ntqwhatsthis.html">TQWhatsThis</a> (for simple help) and a
<p> It also illustrates some aspects of <ahref="tqwhatsthis.html">TQWhatsThis</a> (for simple help) and a
typical <tt>main()</tt> using <ahref="ntqapplication.html">TQApplication</a>.
<p> Finally, it shows a typical print function based on <ahref="tqprinter.html">TQPrinter</a>.
<p><h2> The declaration of ApplicationWindow
@ -228,7 +228,7 @@ function, as its mouse interface is unusual.
"You can also select the <b>Open</b> command "
"from the <b>File</b> menu.</p>";
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQChar</h1>
<p>This is the complete list of member functions for
<ahref="qchar.html">TQChar</a>, including inherited members.
<ahref="tqchar.html">TQChar</a>, including inherited members.
<p>Almost all the functions in this class are <ahref="threads.html#reentrant">reentrant</a> when TQt is built with thread support. The exception is <ahref="#decomposition"><b>decomposition</b></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 TQCharRef</h1>
<p>This is the complete list of member functions for
<ahref="qcharref.html">TQCharRef</a>, including inherited members.
<ahref="tqcharref.html">TQCharRef</a>, including inherited members.
@ -46,10 +46,10 @@ The TQCharRef class is a helper class for <a href="tqstring.html">TQString</a>.
the assignment will apply to the character in the string from
which you got the reference. That is its whole purpose in life.
The TQCharRef becomes invalid once modifications are made to the
string: if you want to keep the character, copy it into a <ahref="qchar.html">TQChar</a>.
string: if you want to keep the character, copy it into a <ahref="tqchar.html">TQChar</a>.
<p> Most of the TQChar member functions also exist in TQCharRef.
However, they are not explicitly documented here.
<p><p>See also <ahref="tqstring.html#operator[]">TQString::operator[]</a>(), <ahref="tqstring.html#at">TQString::at</a>(), <ahref="qchar.html">TQChar</a>, and <ahref="text.html">Text Related Classes</a>.
<p><p>See also <ahref="tqstring.html#operator[]">TQString::operator[]</a>(), <ahref="tqstring.html#at">TQString::at</a>(), <ahref="tqchar.html">TQChar</a>, and <ahref="text.html">Text Related Classes</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 TQConstString</h1>
<p>This is the complete list of member functions for
<ahref="qconststring.html">TQConstString</a>, including inherited members.
<ahref="tqconststring.html">TQConstString</a>, including inherited members.
Returns the rectangle that is covered by ink if the character
specified by <em>ch</em> were to be drawn at the origin of the coordinate
@ -261,7 +261,7 @@ base line).
<p><p>See also <ahref="#leading">leading</a>() and <ahref="#lineSpacing">lineSpacing</a>().
<p>Examples: <ahref="grapher-nsplugin-example.html#x2741">grapher/grapher.cpp</a>, <ahref="hello-example.html#x1630">hello/hello.cpp</a>, and <ahref="qfd-example.html#x1986">qfd/fontdisplayer.cpp</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 TQLabel</h1>
<p>This is the complete list of member functions for
<ahref="ntqlabel.html">TQLabel</a>, including inherited members.
<ahref="tqlabel.html">TQLabel</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 TQLocale</h1>
<p>This is the complete list of member functions for
<ahref="ntqlocale.html">TQLocale</a>, including inherited members.
<ahref="tqlocale.html">TQLocale</a>, including inherited members.
<p>Almost all the functions in this class are <ahref="threads.html#reentrant">reentrant</a> when TQt is built with thread support. The exception is <ahref="#setDefault"><b>setDefault</b></a>().
@ -82,7 +82,7 @@ TQMimeSourceFactory to resolve references such as images or links
within rich text documents. They either access the default factory
(see <ahref="#defaultFactory">defaultFactory</a>()) or their own (see
<ahref="tqtextedit.html#setMimeSourceFactory">TQTextEdit::setMimeSourceFactory</a>()). Other classes that are
capable of displaying rich text (such as <ahref="ntqlabel.html">TQLabel</a>, <ahref="ntqwhatsthis.html">TQWhatsThis</a> or
capable of displaying rich text (such as <ahref="tqlabel.html">TQLabel</a>, <ahref="tqwhatsthis.html">TQWhatsThis</a> or
<ahref="ntqmessagebox.html">TQMessageBox</a>) always use the default factory.
<p> A factory can also be used as a container to store data associated
with a name. This technique is useful whenever rich text contains
@ -105,7 +105,7 @@ insert it into the factory with a unique name:
<p> Now you can create a rich text TQLabel with
<p><pre>
<ahref="ntqlabel.html">TQLabel</a>* label = new <ahref="ntqlabel.html">TQLabel</a>(
<ahref="tqlabel.html">TQLabel</a>* label = new <ahref="tqlabel.html">TQLabel</a>(
"Rich text with embedded image:<img source=\"myimage\">"
"Isn't that <em>cute</em>?" );
</pre>
@ -193,7 +193,7 @@ file name is given in <em>abs_or_rel_name</em> and the path is in <em>context</e
</h3>
Returns the application-wide default mime source factory. This
factory is used by rich text rendering classes such as
<ahref="ntqsimplerichtext.html">TQSimpleRichText</a>, <ahref="ntqwhatsthis.html">TQWhatsThis</a> and <ahref="ntqmessagebox.html">TQMessageBox</a> to resolve named
<ahref="tqsimplerichtext.html">TQSimpleRichText</a>, <ahref="tqwhatsthis.html">TQWhatsThis</a> and <ahref="ntqmessagebox.html">TQMessageBox</a> to resolve named
references within rich text documents. It serves also as the
initial factory for the more complex render widgets, <ahref="tqtextedit.html">TQTextEdit</a> and
<p><p>See also <ahref="#readEntry">readEntry</a>(), <ahref="#readDoubleEntry">readDoubleEntry</a>(), <ahref="#readBoolEntry">readBoolEntry</a>(), <ahref="#writeEntry">writeEntry</a>(), <ahref="#removeEntry">removeEntry</a>(), and <ahref="tqstringlist.html#split">TQStringList::split</a>().
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
<p><b>This function is obsolete.</b> It is provided to keep old source working. We strongly advise against using it in new code.
@ -592,7 +592,7 @@ by <em>value</em>.
returned; otherwise returns TRUE.
<p><p>See also <ahref="#readListEntry">readListEntry</a>(), <ahref="#readNumEntry">readNumEntry</a>(), <ahref="#readDoubleEntry">readDoubleEntry</a>(), <ahref="#readBoolEntry">readBoolEntry</a>(), and <ahref="#removeEntry">removeEntry</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 TQSimpleRichText</h1>
<p>This is the complete list of member functions for
<ahref="ntqsimplerichtext.html">TQSimpleRichText</a>, including inherited members.
<ahref="tqsimplerichtext.html">TQSimpleRichText</a>, including inherited members.
<p><em>Normal</em> and <em>Permanent</em> messages are displayed by creating a
small widget and then adding it to the status bar with
<ahref="#addWidget">addWidget</a>(). Widgets like <ahref="ntqlabel.html">TQLabel</a>, <ahref="ntqprogressbar.html">TQProgressBar</a> or even <ahref="tqtoolbutton.html">TQToolButton</a>
<ahref="#addWidget">addWidget</a>(). Widgets like <ahref="tqlabel.html">TQLabel</a>, <ahref="ntqprogressbar.html">TQProgressBar</a> or even <ahref="tqtoolbutton.html">TQToolButton</a>
are useful for adding to status bars. <ahref="#removeWidget">removeWidget</a>() is used to
remove widgets.
<p><pre>
@ -112,7 +112,7 @@ remove widgets.
<p> By default TQStatusBar provides a <ahref="tqsizegrip.html">TQSizeGrip</a> in the lower-right
corner. You can disable it with <ahref="#setSizeGripEnabled">setSizeGripEnabled</a>(FALSE);
<p><p>See also <ahref="tqtoolbar.html">TQToolBar</a>, <ahref="tqmainwindow.html">TQMainWindow</a>, <ahref="ntqlabel.html">TQLabel</a>, <ahref="guibooks.html#fowler">GUI Design Handbook: Status Bar</a>, <ahref="application.html">Main Window and Related Classes</a>, and <ahref="helpsystem.html">Help System</a>.
<p><p>See also <ahref="tqtoolbar.html">TQToolBar</a>, <ahref="tqmainwindow.html">TQMainWindow</a>, <ahref="tqlabel.html">TQLabel</a>, <ahref="guibooks.html#fowler">GUI Design Handbook: Status Bar</a>, <ahref="application.html">Main Window and Related Classes</a>, and <ahref="helpsystem.html">Help System</a>.
@ -253,7 +253,7 @@ parameters, the <tt>const char *</tt> is interpreted as a classic
C-style '\0'-terminated ASCII string. It is legal for the <tt>const char *</tt> parameter to be 0. If the <tt>const char *</tt> is not
'\0'-terminated, the results are undefined. Functions that copy
classic C strings into a TQString will not copy the terminating
'\0' character. The <ahref="qchar.html">TQChar</a> array of the TQString (as returned by
'\0' character. The <ahref="tqchar.html">TQChar</a> array of the TQString (as returned by
<ahref="#unicode">unicode</a>()) is generally not terminated by a '\0'. If you need to
pass a TQString to a function that requires a C '\0'-terminated
string use <ahref="#latin1">latin1</a>().
@ -317,7 +317,7 @@ shared classes) operates on a copy-on-write basis, only copying if
an instance is actually changed.
<p> If you wish to create a <ahref="shclass.html#deep-copy">deep copy</a> of a TQString without losing any
Unicode information then you should use <ahref="tqdeepcopy.html">TQDeepCopy</a>.
<p><p>See also <ahref="qchar.html">TQChar</a>, <ahref="tqcstring.html">TQCString</a>, <ahref="tqbytearray.html">TQByteArray</a>, <ahref="qconststring.html">TQConstString</a>, <ahref="shared.html">Implicitly and Explicitly Shared Classes</a>, <ahref="text.html">Text Related Classes</a>, and <ahref="tools.html">Non-GUI Classes</a>.
<p><p>See also <ahref="tqchar.html">TQChar</a>, <ahref="tqcstring.html">TQCString</a>, <ahref="tqbytearray.html">TQByteArray</a>, <ahref="tqconststring.html">TQConstString</a>, <ahref="shared.html">Implicitly and Explicitly Shared Classes</a>, <ahref="text.html">Text Related Classes</a>, and <ahref="tools.html">Non-GUI Classes</a>.
double d = <ahref="#TQString">TQString</a>( "1,234,567.89" ).toDouble(&ok); // ok == false
</pre>
<p><b>Warning:</b> If the string contains trailing whitespace this function
will fail, and set <em>*ok</em> to false if <em>ok</em> is not 0. Leading
whitespace is ignored.
<p><p>See also <ahref="#number">number</a>(), <ahref="ntqlocale.html#setDefault">TQLocale::setDefault</a>(), <ahref="ntqlocale.html#toDouble">TQLocale::toDouble</a>(), and <ahref="#stripWhiteSpace">stripWhiteSpace</a>().
<p><p>See also <ahref="#number">number</a>(), <ahref="tqlocale.html#setDefault">TQLocale::setDefault</a>(), <ahref="tqlocale.html#toDouble">TQLocale::toDouble</a>(), and <ahref="#stripWhiteSpace">stripWhiteSpace</a>().
@ -67,9 +67,9 @@ rendering and a generator of tags.
definition of a set of tags. This definition will be used by the
internal rich text rendering system to parse and display text
documents to which the style sheet applies. Rich text is normally
visualized in a <ahref="tqtextedit.html">TQTextEdit</a> or a <ahref="tqtextbrowser.html">TQTextBrowser</a>. However, <ahref="ntqlabel.html">TQLabel</a>,
<ahref="ntqwhatsthis.html">TQWhatsThis</a> and <ahref="ntqmessagebox.html">TQMessageBox</a> also support it, and other classes are
likely to follow. With <ahref="ntqsimplerichtext.html">TQSimpleRichText</a> it is possible to use the
visualized in a <ahref="tqtextedit.html">TQTextEdit</a> or a <ahref="tqtextbrowser.html">TQTextBrowser</a>. However, <ahref="tqlabel.html">TQLabel</a>,
<ahref="tqwhatsthis.html">TQWhatsThis</a> and <ahref="ntqmessagebox.html">TQMessageBox</a> also support it, and other classes are
likely to follow. With <ahref="tqsimplerichtext.html">TQSimpleRichText</a> it is possible to use the
rich text renderer for custom widgets as well.
<p> The default TQStyleSheet object has the following style bindings,
sorted by structuring bindings, anchors, character style bindings
@ -90,7 +90,7 @@ page of its own. Another style is <tt>detail</tt>, which can be
used to explain certain expressions in more detail in a
few sentences. For <tt>detail</tt>, <ahref="tqtextbrowser.html">TQTextBrowser</a> will then keep
the current page and display the new document in a small
popup similar to <ahref="ntqwhatsthis.html">TQWhatsThis</a>. Note that links will not work
popup similar to <ahref="tqwhatsthis.html">TQWhatsThis</a>. Note that links will not work
in documents with <tt><qt type="detail">...</qt></tt>.
<li><tt>bgcolor</tt> -- The background color, for example <tt>bgcolor="yellow"</tt> or <tt>bgcolor="#0000FF"</tt>.
<li><tt>background</tt> -- The background pixmap, for example <tt>background="granite.xpm"</tt>. The pixmap name will be resolved
<tdalign="right"valign="center"><imgsrc="logo32.png"align="right"width="64"height="32"border="0"></td></tr></table><h1align=center>Complete Member List for TQSyntaxHighlighter</h1>
<p>This is the complete list of member functions for
<ahref="ntqsyntaxhighlighter.html">TQSyntaxHighlighter</a>, including inherited members.
<ahref="tqsyntaxhighlighter.html">TQSyntaxHighlighter</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 TQWhatsThis</h1>
<p>This is the complete list of member functions for
<ahref="ntqwhatsthis.html">TQWhatsThis</a>, including inherited members.
<ahref="tqwhatsthis.html">TQWhatsThis</a>, including inherited members.
</h3><p>Sets the font currently set for the widget.
See the <ahref="tqwidget.html#font-prop">"font"</a> property for details.
<p>Reimplemented in <ahref="ntqcombobox.html#setFont">TQComboBox</a>, <ahref="ntqlabel.html#setFont">TQLabel</a>, and <ahref="ntqtabdialog.html#setFont">TQTabDialog</a>.
<p>Reimplemented in <ahref="ntqcombobox.html#setFont">TQComboBox</a>, <ahref="tqlabel.html#setFont">TQLabel</a>, and <ahref="ntqtabdialog.html#setFont">TQTabDialog</a>.
which means the widget will not receive any events in Whats This
mode.
<p> The widget may leave What's This mode by calling
<ahref="ntqwhatsthis.html#leaveWhatsThisMode">TQWhatsThis::leaveWhatsThisMode</a>(), with or without actually
<ahref="tqwhatsthis.html#leaveWhatsThisMode">TQWhatsThis::leaveWhatsThisMode</a>(), with or without actually
displaying any help text.
<p> You can also reimplement customWhatsThis() if your widget is a
"passive interactor" supposed to work under all circumstances.
Simply don't call TQWhatsThis::leaveWhatsThisMode() in that case.
<p><p>See also <ahref="ntqwhatsthis.html#inWhatsThisMode">TQWhatsThis::inWhatsThisMode</a>() and <ahref="ntqwhatsthis.html#leaveWhatsThisMode">TQWhatsThis::leaveWhatsThisMode</a>().
<p><p>See also <ahref="tqwhatsthis.html#inWhatsThisMode">TQWhatsThis::inWhatsThisMode</a>() and <ahref="tqwhatsthis.html#leaveWhatsThisMode">TQWhatsThis::leaveWhatsThisMode</a>().
<p>Get this property's value with <ahref="#customWhatsThis">customWhatsThis</a>().
@ -80,7 +80,7 @@ all user-visible strings, and performing all text file I/O using
widgets you write; it does not make much difference for slow typists
in Western Europe or North America, but for fast typists or people
using special input methods using text() is beneficial.
<p> All the function arguments in TQt that may be user-visible strings, <ahref="ntqlabel.html#setText">TQLabel::setText</a>() and a many others, take <tt>const TQString &</tt>s.
<p> All the function arguments in TQt that may be user-visible strings, <ahref="tqlabel.html#setText">TQLabel::setText</a>() and a many others, take <tt>const TQString &</tt>s.
<ahref="tqstring.html">TQString</a> provides implicit casting from <tt>const char *</tt>
@ -102,7 +102,7 @@ The QAccel 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
In most cases, you will not need to use this class directly. Use the TQAction class to create actions with accelerators that can be used in both menus and toolbars. If you're only interested in menus use TQMenuData::insertItem() or TQMenuData::setAccel() to make accelerators for operations that are also available on menus. Many widgets automatically generate accelerators, such as QButton, QGroupBox, QLabel (with QLabel::setBuddy()), TQMenuBar and QTabBar. Example:
In most cases, you will not need to use this class directly. Use the TQAction class to create actions with accelerators that can be used in both menus and toolbars. If you're only interested in menus use TQMenuData::insertItem() or TQMenuData::setAccel() to make accelerators for operations that are also available on menus. Many widgets automatically generate accelerators, such as QButton, QGroupBox, TQLabel (with TQLabel::setBuddy()), TQMenuBar and QTabBar. Example:
.PP
.nf
.br
@ -120,7 +120,7 @@ Each accelerator item consists of an identifier and a QKeySequence. A single key
.PP
When an accelerator key is pressed, the accelerator sends out the signal activated() with a number that identifies this particular accelerator item. Accelerator items can also be individually connected, so that two different keys will activate two different slots (see connectItem() and disconnectItem()).
.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 QPushButton and QCheckBox connect the activatedAmbiguously() signal to the harmless setFocus() slot, whereas activated() is connected to a slot invoking the button's action. Most controls, like QLabel and QTabBar, treat activated() and activatedAmbiguously() as equivalent.
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 QPushButton and QCheckBox 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 QTabBar, 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.
.PP
@ -151,7 +151,7 @@ Example:
.br
.fi
.PP
See also QKeyEvent, TQWidget::keyPressEvent(), TQMenuData::setAccel(), QButton::accel, QLabel::setBuddy(), QKeySequence, GUI Design Handbook: Keyboard Shortcuts, and Miscellaneous Classes.
See also QKeyEvent, TQWidget::keyPressEvent(), TQMenuData::setAccel(), QButton::accel, TQLabel::setBuddy(), QKeySequence, GUI Design Handbook: Keyboard Shortcuts, and Miscellaneous Classes.
@ -366,7 +366,7 @@ Notifies accessibility clients about a change in \fIobject\fR's accessibility in
.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.
.PP
Call this function whenever the state of your accessible object or one of it's sub-elements has been changed either programmatically (e.g. by calling QLabel::setText()) or by user interaction.
Call this function whenever the state of your accessible object or one of it's sub-elements has been changed either programmatically (e.g. by calling TQLabel::setText()) or by user interaction.
.PP
If there are no accessibility tools listening to this event, the
performance penalty for calling this function is minor, but if determining
@ -506,7 +506,7 @@ This property holds the action's "What's This?" help text.
.PP
The whats this text is used to provide a brief description of the action. The text may contain rich text (HTML-like tags -- see TQStyleSheet for the list of supported tags). There is no default" What's This" text.
.PP
See also QWhatsThis.
See also TQWhatsThis.
.PP
Set this property's value with setWhatsThis() and get this property's value with whatsThis().
.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the
.\" license file included in the distribution for a complete license
.\" statement.
@ -7,23 +7,23 @@
.ad l
.nh
.SH NAME
QCharRef \- Helper class for TQString
TQCharRef \- Helper class for TQString
.SH SYNOPSIS
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <tqstring.h>\fR
.PP
.SH DESCRIPTION
The QCharRef class is a helper class for TQString.
The TQCharRef class is a helper class for TQString.
.PP
When you get an object of type QCharRef, if you can assign to it, the assignment will apply to the character in the string from which you got the reference. That is its whole purpose in life. The QCharRef becomes invalid once modifications are made to the string: if you want to keep the character, copy it into a TQChar.
When you get an object of type TQCharRef, if you can assign to it, the assignment will apply to the character in the string from which you got the reference. That is its whole purpose in life. The TQCharRef becomes invalid once modifications are made to the string: if you want to keep the character, copy it into a TQChar.
.PP
Most of the TQChar member functions also exist in QCharRef. However, they are not explicitly documented here.
Most of the TQChar member functions also exist in TQCharRef. However, they are not explicitly documented here.
.PP
See also TQString::operator[](), TQString::at(), TQChar, and Text Related Classes.
.SH "SEE ALSO"
.BR http://doc.trolltech.com/qcharref.html
.BR http://doc.trolltech.com/tqcharref.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
The QConstString class provides string objects using constant Unicode data.
The TQConstString class provides string objects using constant Unicode data.
.PP
In order to minimize copying, highly optimized applications can use QConstString to provide a TQString-compatible object from existing Unicode data. It is then the programmer's responsibility to ensure that the Unicode data exists for the entire lifetime of the QConstString object.
In order to minimize copying, highly optimized applications can use TQConstString to provide a TQString-compatible object from existing Unicode data. It is then the programmer's responsibility to ensure that the Unicode data exists for the entire lifetime of the TQConstString object.
.PP
A QConstString is created with the QConstString constructor. The string held by the object can be obtained by calling string().
A TQConstString is created with the TQConstString constructor. The string held by the object can be obtained by calling string().
Constructs a QConstString that uses the first \fIlength\fR Unicode characters in the array \fIunicode\fR. Any attempt to modify copies of the string will cause it to create a copy of the data, thus it remains forever unmodified.
Constructs a TQConstString that uses the first \fIlength\fR Unicode characters in the array \fIunicode\fR. Any attempt to modify copies of the string will cause it to create a copy of the data, thus it remains forever unmodified.
.PP
The data in \fIunicode\fR is not copied. The caller must be able to guarantee that \fIunicode\fR will not be deleted or modified.
.SH "QConstString::~QConstString ()"
Destroys the QConstString, creating a copy of the data if other strings are still using it.
@ -342,7 +342,7 @@ A preview widget is a widget that is placed inside a TQFileDialog so that the us
.br
.fi
.PP
In the above snippet, we create a preview widget which inherits from QLabel and TQFilePreview. File preview widgets \fImust\fR inherit from TQFilePreview.
In the above snippet, we create a preview widget which inherits from TQLabel and TQFilePreview. File preview widgets \fImust\fR inherit from TQFilePreview.
.PP
Inside the class we reimplement TQFilePreview::previewUrl(), this is where we determine what happens when a file is selected. In the above example we only show a preview of the file if it is a valid pixmap. Here's how to make a file dialog use a preview widget:
.PP
@ -447,7 +447,7 @@ See also addLeftWidget(), addWidgets(), and addToolButton().
Adds the tool button \fIb\fR to the row of tool buttons at the top of the file dialog. The button is appended to the right of this row. If \fIseparator\fR is TRUE, a small space is inserted between the last button of the row and the new button \fIb\fR.
.PP
See also addWidgets(), addLeftWidget(), and addRightWidget().
Adds the specified widgets to the bottom of the file dialog. The label \fIl\fR is placed underneath the "file name" and the "file types" labels. The widget \fIw\fR is placed underneath the file types combobox. The button \fIb\fR is placed underneath the Cancel pushbutton.
.PP
.nf
@ -458,7 +458,7 @@ Adds the specified widgets to the bottom of the file dialog. The label \fIl\fR i
.br
{
.br
QLabel* label = new QLabel( "Added widgets", this );
TQLabel* label = new TQLabel( "Added widgets", this );
.br
QLineEdit* lineedit = new QLineEdit( this );
.br
@ -687,13 +687,13 @@ Normally you would create a preview widget that derives from both TQWidget and T
.PP
.nf
.br
class Preview : public QLabel, public TQFilePreview
class Preview : public TQLabel, public TQFilePreview
@ -13,7 +13,7 @@ QFrame \- The base class of widgets that can have a frame
.PP
Inherits TQWidget.
.PP
Inherited by QGroupBox, QScrollView, QDockWindow, QGrid, QHBox, QLabel, QLCDNumber, QLineEdit, TQMenuBar, TQPopupMenu, QProgressBar, QSplitter, TQToolBox, and TQWidgetStack.
Inherited by QGroupBox, QScrollView, QDockWindow, QGrid, QHBox, TQLabel, QLCDNumber, QLineEdit, TQMenuBar, TQPopupMenu, QProgressBar, QSplitter, TQToolBox, and TQWidgetStack.
.PP
.SS "Public Members"
.in +1c
@ -125,11 +125,11 @@ The QFrame class is the base class of widgets that can have a frame.
.PP
It draws a frame and calls a virtual function, drawContents(), to fill in the frame. This function is reimplemented by subclasses. There are also two other less useful functions: drawFrame() and frameChanged().
.PP
TQPopupMenu uses this to "raise" the menu above the surrounding screen. QProgressBar has a "sunken" look. QLabel has a flat look. The frames of widgets like these can be changed.
TQPopupMenu uses this to "raise" the menu above the surrounding screen. QProgressBar has a "sunken" look. TQLabel has a flat look. The frames of widgets like these can be changed.
@ -154,7 +154,7 @@ This illustration shows a fragment of a dialog with a five-column, three-row gri
.PP
</center>
.PP
Columns 0, 2 and 4 in this dialog fragment are made up of a QLabel, a QLineEdit, and a QListBox. Columns 1 and 3 are placeholders made with addColSpacing(). Row 0 consists of three QLabel objects, row 1 of three QLineEdit objects and row 2 of three QListBox objects. We used placeholder columns (1 and 3) to get the right amount of space between the columns.
Columns 0, 2 and 4 in this dialog fragment are made up of a TQLabel, a QLineEdit, and a QListBox. Columns 1 and 3 are placeholders made with addColSpacing(). Row 0 consists of three TQLabel objects, row 1 of three QLineEdit objects and row 2 of three QListBox objects. We used placeholder columns (1 and 3) to get the right amount of space between the columns.
.PP
Note that the columns and rows are not equally wide or tall. If you want two columns to have the same width, you must set their minimum widths and stretch factors to be the same yourself. You do this using addColSpacing() and setColStretch().
@ -44,7 +44,7 @@ Transforms the logically ordered TQString, \fIuc\fR, into a visually ordered str
.PP
The algorithm is designed to work on whole paragraphs of text, so processing a line at a time may produce incorrect results. This approach is taken because the reordering of the contents of a particular line in a paragraph may depend on the previous line in the same paragraph.
.PP
Some encodings (for example Japanese or UTF-8) are multibyte (so one input character is mapped to two output characters). The \fIlenInOut\fR argument specifies the number of QChars that should be converted and is set to the number of characters returned.
Some encodings (for example Japanese or UTF-8) are multibyte (so one input character is mapped to two output characters). The \fIlenInOut\fR argument specifies the number of TQChars that should be converted and is set to the number of characters returned.
@ -38,7 +38,7 @@ TQImageConsumer \- Abstraction used by TQImageDecoder
.SH DESCRIPTION
The TQImageConsumer class is an abstraction used by TQImageDecoder.
.PP
The TQMovie class, or QLabel::setMovie(), are easy to use and for most situations do what you want with regards animated images.
The TQMovie class, or TQLabel::setMovie(), are easy to use and for most situations do what you want with regards animated images.
.PP
A TQImageConsumer consumes information about changes to the TQImage maintained by a TQImageDecoder. Think of the TQImage as the model or source of the image data, with the TQImageConsumer as a view of that data and the TQImageDecoder being the controller that orchestrates the relationship between the model and the view.
The QLabel widget provides a text or image display.
The TQLabel widget provides a text or image display.
.PP
QLabel is used for displaying text or an image. No user interaction functionality is provided. The visual appearance of the label can be configured in various ways, and it can be used for specifying a focus accelerator key for another widget.
TQLabel is used for displaying text or an image. No user interaction functionality is provided. The visual appearance of the label can be configured in various ways, and it can be used for specifying a focus accelerator key for another widget.
.PP
A QLabel can contain any of the following content types: <center>.nf
A TQLabel can contain any of the following content types: <center>.nf
.TS
l - l. Content Setting Plain text Pass a TQString to setText(). Rich text Pass a TQString that contains rich text to setText(). A pixmap Pass a TQPixmap to setPixmap(). A movie Pass a TQMovie to setMovie(). A number Pass an \fIint\fR or a \fIdouble\fR to setNum(), which converts the number to plain text. Nothing
.TE
@ -147,11 +147,11 @@ l - l. Content Setting Plain text Pass a TQString to setText(). Rich text Pass a
.PP
When the content is changed using any of these functions, any previous content is cleared.
.PP
The look of a QLabel can be tuned in several ways. All the settings of QFrame are available for specifying a widget frame. The positioning of the content within the QLabel widget area can be tuned with setAlignment() and setIndent(). For example, this code sets up a sunken panel with a two-line text in the bottom right corner (both lines being flush with the right side of the label):
The look of a TQLabel can be tuned in several ways. All the settings of QFrame are available for specifying a widget frame. The positioning of the content within the TQLabel widget area can be tuned with setAlignment() and setIndent(). For example, this code sets up a sunken panel with a two-line text in the bottom right corner (both lines being flush with the right side of the label):
@ -161,13 +161,13 @@ The look of a QLabel can be tuned in several ways. All the settings of QFrame ar
.br
.fi
.PP
A QLabel is often used as a label for an interactive widget. For this use QLabel provides a useful mechanism for adding an accelerator key (see QAccel) that will set the keyboard focus to the other widget (called the QLabel'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 QAccel) that will set the keyboard focus to the other widget (called the TQLabel's "buddy"). For example:
.PP
.nf
.br
QLineEdit* phoneEdit = new QLineEdit( this, "phoneEdit" );
.br
QLabel* phoneLabel = new QLabel( phoneEdit, "&Phone:", this, "phoneLabel" );
TQLabel* phoneLabel = new TQLabel( phoneEdit, "&Phone:", this, "phoneLabel" );
.br
.fi
.PP
@ -182,19 +182,19 @@ In this example, keyboard focus is transferred to the label's buddy (the QLineEd
.PP
See also QLineEdit, TQTextEdit, TQPixmap, TQMovie, GUI Design Handbook: Label, Basic Widgets, and Text Related Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QLabel::QLabel ( TQWidget * parent, const char * name = 0, WFlags f = 0 )"
.SH "TQLabel::TQLabel ( TQWidget * parent, const char * name = 0, WFlags f = 0 )"
Constructs an empty label.
.PP
The \fIparent\fR, \fIname\fR and widget flag \fIf\fR, arguments are passed to the QFrame constructor.
Constructs a label that displays the text \fItext\fR. The label has a buddy widget, \fIbuddy\fR.
.PP
If the \fItext\fR contains an underlined letter (a letter preceded by an ampersand, &), and the text is in plain text format, when the user presses Alt+ the underlined letter, focus is passed to the buddy widget.
@ -202,11 +202,11 @@ If the \fItext\fR contains an underlined letter (a letter preceded by an ampersa
The \fIparent\fR, \fIname\fR and widget flag, \fIf\fR, arguments are passed to the QFrame constructor.
.PP
See also text, setBuddy(), alignment, setFrameStyle(), and indent.
.SH "QLabel::~QLabel ()"
.SH "TQLabel::~TQLabel ()"
Destroys the label.
.SH "int QLabel::alignment () const"
.SH "int TQLabel::alignment () const"
Returns the alignment of the label's contents. See the "alignment" property for details.
.SH "bool QLabel::autoResize () const"
.SH "bool TQLabel::autoResize () const"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Returns TRUE if auto-resizing is enabled, or FALSE if auto-resizing is disabled.
@ -214,46 +214,46 @@ Returns TRUE if auto-resizing is enabled, or FALSE if auto-resizing is disabled.
Auto-resizing is disabled by default.
.PP
See also setAutoResize().
.SH "TQWidget * QLabel::buddy () const"
.SH "TQWidget * TQLabel::buddy () const"
Returns this label's buddy, or 0 if no buddy is currently set.
.PP
See also setBuddy().
.SH "void QLabel::clear ()\fC [slot]\fR"
.SH "void TQLabel::clear ()\fC [slot]\fR"
Clears any label contents. Equivalent to setText( "" ).
.SH "void QLabel::drawContents ( TQPainter * p )\fC [virtual protected]\fR"
.SH "void TQLabel::drawContents ( TQPainter * p )\fC [virtual protected]\fR"
Draws the label contents using the painter \fIp\fR.
.PP
Reimplemented from QFrame.
.SH "bool QLabel::hasScaledContents () const"
.SH "bool TQLabel::hasScaledContents () const"
Returns TRUE if the label will scale its contents to fill all available space; otherwise returns FALSE. See the "scaledContents" property for details.
.SH "int QLabel::indent () const"
.SH "int TQLabel::indent () const"
Returns the label's text indent in pixels. See the "indent" property for details.
.SH "TQMovie * QLabel::movie () const"
.SH "TQMovie * TQLabel::movie () const"
Returns a pointer to the label's movie, or 0 if no movie has been set.
.PP
See also setMovie().
.SH "TQPicture * QLabel::picture () const"
.SH "TQPicture * TQLabel::picture () const"
Returns the label's picture or 0 if the label doesn't have a picture.
.SH "TQPixmap * QLabel::pixmap () const"
.SH "TQPixmap * TQLabel::pixmap () const"
Returns the label's pixmap. See the "pixmap" property for details.
.SH "void QLabel::setAlignment ( int )\fC [virtual]\fR"
.SH "void TQLabel::setAlignment ( int )\fC [virtual]\fR"
Sets the alignment of the label's contents. See the "alignment" property for details.
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Enables auto-resizing if \fIenable\fR is TRUE, or disables it if \fIenable\fR is FALSE.
.PP
When auto-resizing is enabled the label will resize itself to fit the contents whenever the contents change. The top-left corner is not moved. This is useful for QLabel widgets that are not managed by a QLayout (e.g., top-level widgets).
When auto-resizing is enabled the label will resize itself to fit the contents whenever the contents change. The top-left corner is not moved. This is useful for TQLabel widgets that are not managed by a QLayout (e.g., top-level widgets).
.PP
Auto-resizing is disabled by default.
.PP
See also autoResize(), adjustSize(), and sizeHint.
When the user presses the accelerator key indicated by this label, the keyboard focus is transferred to the label's buddy widget.
.PP
The buddy mechanism is only available for QLabels that contain plain text in which one letter is prefixed with an ampersand, &. This letter is set as the accelerator key. The letter is displayed underlined, and the '&' is not displayed (i.e. the ShowPrefix alignment flag is turned on; see setAlignment()).
The buddy mechanism is only available for TQLabels that contain plain text in which one letter is prefixed with an ampersand, &. This letter is set as the accelerator key. The letter is displayed underlined, and the '&' is not displayed (i.e. the ShowPrefix alignment flag is turned on; see setAlignment()).
.PP
In a dialog, you might create two data entry widgets and a label for each, and set up the geometry layout so each label is just to the left of its data entry widget (its "buddy"), for example:
.PP
@ -261,13 +261,13 @@ In a dialog, you might create two data entry widgets and a label for each, and s
.br
QLineEdit *nameEd = new QLineEdit( this );
.br
QLabel *nameLb = new QLabel( "&Name:", this );
TQLabel *nameLb = new TQLabel( "&Name:", this );
.br
nameLb->setBuddy( nameEd );
.br
QLineEdit *phoneEd = new QLineEdit( this );
.br
QLabel *phoneLb = new QLabel( "&Phone:", this );
TQLabel *phoneLb = new TQLabel( "&Phone:", this );
.br
phoneLb->setBuddy( phoneEd );
.br
@ -283,15 +283,15 @@ See also buddy(), text, QAccel, and alignment.
.PP
Examples:
.)l addressbook/centralwidget.cpp, chart/optionsform.cpp, and regexptester/regexptester.cpp.
.SH "void QLabel::setFont ( const TQFont & f )\fC [virtual]\fR"
Sets the font used on the QLabel to font \fIf\fR.
.SH "void TQLabel::setFont ( const TQFont & f )\fC [virtual]\fR"
Sets the font used on the TQLabel to font \fIf\fR.
.PP
Example: menu/menu.cpp.
.PP
Reimplemented from TQWidget.
.SH "void QLabel::setIndent ( int )"
.SH "void TQLabel::setIndent ( int )"
Sets the label's text indent in pixels. See the "indent" property for details.
Sets the label contents to \fImovie\fR. Any previous content is cleared.
.PP
The buddy accelerator, if any, is disabled.
@ -299,7 +299,7 @@ The buddy accelerator, if any, is disabled.
The label resizes itself if auto-resizing is enabled.
.PP
See also movie() and setBuddy().
.SH "void QLabel::setNum ( int num )\fC [virtual slot]\fR"
.SH "void TQLabel::setNum ( int num )\fC [virtual slot]\fR"
Sets the label contents to plain text containing the textual representation of integer \fInum\fR. Any previous content is cleared. Does nothing if the integer's string representation is the same as the current contents of the label.
.PP
The buddy accelerator, if any, is disabled.
@ -307,7 +307,7 @@ The buddy accelerator, if any, is disabled.
The label resizes itself if auto-resizing is enabled.
.PP
See also text, TQString::setNum(), and setBuddy().
.SH "void QLabel::setNum ( double num )\fC [virtual slot]\fR"
.SH "void TQLabel::setNum ( double num )\fC [virtual slot]\fR"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Sets the label contents to plain text containing the textual representation of double \fInum\fR. Any previous content is cleared. Does nothing if the double's string representation is the same as the current contents of the label.
@ -317,29 +317,29 @@ The buddy accelerator, if any, is disabled.
The label resizes itself if auto-resizing is enabled.
.PP
See also text, TQString::setNum(), and setBuddy().
Sets the label's text. See the "text" property for details.
.SH "void QLabel::setTextFormat ( TextFormat )"
.SH "void TQLabel::setTextFormat ( TextFormat )"
Sets the label's text format. See the "textFormat" property for details.
.SH "TQString QLabel::text () const"
.SH "TQString TQLabel::text () const"
Returns the label's text. See the "text" property for details.
.SH "TextFormat QLabel::textFormat () const"
.SH "TextFormat TQLabel::textFormat () const"
Returns the label's text format. See the "textFormat" property for details.
.SS "Property Documentation"
.SH "Alignment alignment"
This property holds the alignment of the label's contents.
.PP
The alignment is a bitwise OR of TQt::AlignmentFlags and TQt::TextFlags values. The ExpandTabs, SingleLine and ShowPrefix flags apply only if the label contains plain text; otherwise they are ignored. The DontClip flag is always ignored. WordBreak applies to both rich text and plain text labels. The BreakAnywhere flag is not supported in QLabel.
The alignment is a bitwise OR of TQt::AlignmentFlags and TQt::TextFlags values. The ExpandTabs, SingleLine and ShowPrefix flags apply only if the label contains plain text; otherwise they are ignored. The DontClip flag is always ignored. WordBreak applies to both rich text and plain text labels. The BreakAnywhere flag is not supported in TQLabel.
.PP
If the label has a buddy, the ShowPrefix flag is forced to TRUE.
.PP
@ -369,7 +369,7 @@ This property holds the label's pixmap.
.PP
If no pixmap has been set this will return an invalid pixmap.
.PP
Setting the pixmap clears any previous content, and resizes the label if QLabel::autoResize() is TRUE. The buddy accelerator, if any, is disabled.
Setting the pixmap clears any previous content, and resizes the label if TQLabel::autoResize() is TRUE. The buddy accelerator, if any, is disabled.
.PP
Set this property's value with setPixmap() and get this property's value with pixmap().
.SH "bool scaledContents"
@ -387,13 +387,13 @@ This property holds the label's text.
.PP
If no text has been set this will return an empty string. Setting the text clears any previous content, unless they are the same.
.PP
The text will be interpreted either as a plain text or as a rich text, depending on the text format setting; see setTextFormat(). The default setting is AutoText, i.e. QLabel will try to auto-detect the format of the text set.
The text will be interpreted either as a plain text or as a rich text, depending on the text format setting; see setTextFormat(). The default setting is AutoText, i.e. TQLabel will try to auto-detect the format of the text set.
.PP
If the text is interpreted as a plain text and a buddy has been set, the buddy accelerator key is updated from the new text.
.PP
The label resizes itself if auto-resizing is enabled.
.PP
Note that Qlabel is well-suited to display small rich text documents, i.e. those small documents that get their document specific settings (font, text color, link color) from the label's palette and font properties. For large documents, use TQTextEdit in read-only mode instead. TQTextEdit will flicker less on resize and can also provide a scrollbar when necessary.
Note that TQLabel is well-suited to display small rich text documents, i.e. those small documents that get their document specific settings (font, text color, link color) from the label's palette and font properties. For large documents, use TQTextEdit in read-only mode instead. TQTextEdit will flicker less on resize and can also provide a scrollbar when necessary.
.PP
See also textFormat, setBuddy(), and alignment.
.PP
@ -410,7 +410,7 @@ See also text.
Set this property's value with setTextFormat() and get this property's value with textFormat().
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqlabel.html
.BR http://doc.trolltech.com/tqlabel.html
.BR http://www.trolltech.com/faq/tech.html
.SH COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the
Enters 'What's This?' mode and returns immediately.
.PP
This is the same as QWhatsThis::enterWhatsThisMode(), but implemented as a main window object's slot. This way it can easily be used for popup menus, for example:
This is the same as TQWhatsThis::enterWhatsThisMode(), but implemented as a main window object's slot. This way it can easily be used for popup menus, for example:
.PP
.nf
.br
@ -755,7 +755,7 @@ This is the same as QWhatsThis::enterWhatsThisMode(), but implemented as a main
.br
.fi
.PP
See also QWhatsThis::enterWhatsThisMode().
See also TQWhatsThis::enterWhatsThisMode().
.SS "Property Documentation"
.SH "bool dockWindowsMovable"
This property holds whether the dock windows are movable.
@ -445,7 +445,7 @@ Ownership of \fIwidget\fR is transferred to the popup menu or to the menu bar.
.PP
Theoretically, any widget can be inserted into a popup menu. In practice, this only makes sense with certain widgets.
.PP
If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a QLabel if you need a popup menu with a title.
If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a TQLabel if you need a popup menu with a title.
.PP
If the widget is focus-enabled it will get focus when the user traverses the popup menu with the arrow keys. If the widget does not accept \fCArrowUp\fR and \fCArrowDown\fR in its key event handler, the focus will move back to the menu when the respective arrow key is hit one more time. This works with a QLineEdit, for example. If the widget accepts the arrow key itself, it must also provide the possibility to put the focus back on the menu again by calling TQWidget::focusNextPrevChild(). Futhermore, if the embedded widget closes the menu when the user made a selection, this can be done safely by calling:
@ -485,7 +485,7 @@ Ownership of \fIwidget\fR is transferred to the popup menu or to the menu bar.
.PP
Theoretically, any widget can be inserted into a popup menu. In practice, this only makes sense with certain widgets.
.PP
If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a QLabel if you need a popup menu with a title.
If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a TQLabel if you need a popup menu with a title.
.PP
If the widget is focus-enabled it will get focus when the user traverses the popup menu with the arrow keys. If the widget does not accept \fCArrowUp\fR and \fCArrowDown\fR in its key event handler, the focus will move back to the menu when the respective arrow key is hit one more time. This works with a QLineEdit, for example. If the widget accepts the arrow key itself, it must also provide the possibility to put the focus back on the menu again by calling TQWidget::focusNextPrevChild(). Futhermore, if the embedded widget closes the menu when the user made a selection, this can be done safely by calling:
@ -78,7 +78,7 @@ A TQMimeSourceFactory provides an abstract interface to a collection of informat
.PP
The base TQMimeSourceFactory can be used in two ways: as an abstraction of a collection of files or as specifically stored data. For it to access files, call setFilePath() before accessing data. For stored data, call setData() for each item (there are also convenience functions, e.g. setText(), setImage() and setPixmap(), that simply call setData() with appropriate parameters).
.PP
The rich text widgets, TQTextEdit and TQTextBrowser, use TQMimeSourceFactory to resolve references such as images or links within rich text documents. They either access the default factory (see defaultFactory()) or their own (see TQTextEdit::setMimeSourceFactory()). Other classes that are capable of displaying rich text (such as QLabel, QWhatsThis or QMessageBox) always use the default factory.
The rich text widgets, TQTextEdit and TQTextBrowser, use TQMimeSourceFactory to resolve references such as images or links within rich text documents. They either access the default factory (see defaultFactory()) or their own (see TQTextEdit::setMimeSourceFactory()). Other classes that are capable of displaying rich text (such as TQLabel, TQWhatsThis or QMessageBox) always use the default factory.
.PP
A factory can also be used as a container to store data associated with a name. This technique is useful whenever rich text contains images that are stored in the program itself, not loaded from the hard disk. Your program may, for example, define some image data as:
.PP
@ -94,7 +94,7 @@ A factory can also be used as a container to store data associated with a name.
.br
.fi
.PP
To be able to use this image within some rich text, for example inside a QLabel, you must create a TQImage from the raw data and insert it into the factory with a unique name:
To be able to use this image within some rich text, for example inside a TQLabel, you must create a TQImage from the raw data and insert it into the factory with a unique name:
.PP
.nf
.br
@ -102,11 +102,11 @@ To be able to use this image within some rich text, for example inside a QLabel,
.br
.fi
.PP
Now you can create a rich text QLabel with
Now you can create a rich text TQLabel with
.PP
.nf
.br
QLabel* label = new QLabel(
TQLabel* label = new TQLabel(
.br
"Rich text with embedded image:<img source=\\"myimage\\">"
.br
@ -166,7 +166,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
A convenience function. See data(const TQString& abs_name). The file name is given in \fIabs_or_rel_name\fR and the path is in \fIcontext\fR.
Returns the application-wide default mime source factory. This factory is used by rich text rendering classes such as QSimpleRichText, QWhatsThis and QMessageBox to resolve named references within rich text documents. It serves also as the initial factory for the more complex render widgets, TQTextEdit and TQTextBrowser.
Returns the application-wide default mime source factory. This factory is used by rich text rendering classes such as TQSimpleRichText, TQWhatsThis and QMessageBox to resolve named references within rich text documents. It serves also as the initial factory for the more complex render widgets, TQTextEdit and TQTextBrowser.
@ -122,7 +122,7 @@ TQMovie \- Incremental loading of animations or images, signalling as it progres
.SH DESCRIPTION
The TQMovie class provides incremental loading of animations or images, signalling as it progresses.
.PP
The simplest way to display a TQMovie is to use a QLabel and QLabel::setMovie().
The simplest way to display a TQMovie is to use a TQLabel and TQLabel::setMovie().
.PP
A TQMovie provides a TQPixmap as the framePixmap(); connections can be made via connectResize() and connectUpdate() to receive notification of size and pixmap changes. All decoding is driven by the normal event-processing mechanisms.
.PP
@ -146,7 +146,7 @@ GIF support may be removed completely in a future version of Qt. We recommend us
.PP
</center>
.PP
See also QLabel::setMovie(), Graphics Classes, Image Processing Classes, and Multimedia Classes.
See also TQLabel::setMovie(), Graphics Classes, Image Processing Classes, and Multimedia Classes.
@ -226,7 +226,7 @@ bitBlt() the pixmap contents onto the widget.
.PP
Pixel data in a pixmap is internal and is managed by the underlying window system. Pixels can be accessed only through TQPainter functions, through bitBlt(), and by converting the TQPixmap to a TQImage.
.PP
You can easily display a TQPixmap on the screen using QLabel::setPixmap(). For example, all the QButton subclasses support pixmap use.
You can easily display a TQPixmap on the screen using TQLabel::setPixmap(). For example, all the QButton subclasses support pixmap use.
.PP
The TQPixmap class uses copy-on-write, so it is practical to pass TQPixmap objects by value.
@ -231,7 +231,7 @@ A popup menu can display check marks for certain items when enabled with setChec
.PP
Items are either enabled or disabled. You toggle their state with setItemEnabled(). Just before a popup menu becomes visible, it emits the aboutToShow() signal. You can use this signal to set the correct enabled/disabled states of all menu items before the user sees it. The corresponding aboutToHide() signal is emitted when the menu hides again.
.PP
You can provide What's This? help for single menu items with setWhatsThis(). See QWhatsThis for general information about this kind of lightweight online help.
You can provide What's This? help for single menu items with setWhatsThis(). See TQWhatsThis for general information about this kind of lightweight online help.
.PP
For ultimate flexibility, you can also add entire widgets as items into a popup menu (for example, a color selector).
.PP
@ -573,7 +573,7 @@ Ownership of \fIwidget\fR is transferred to the popup menu or to the menu bar.
.PP
Theoretically, any widget can be inserted into a popup menu. In practice, this only makes sense with certain widgets.
.PP
If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a QLabel if you need a popup menu with a title.
If a widget is not focus-enabled (see TQWidget::isFocusEnabled()), the menu treats it as a separator; this means that the item is not selectable and will never get focus. In this way you can, for example, simply insert a TQLabel if you need a popup menu with a title.
.PP
If the widget is focus-enabled it will get focus when the user traverses the popup menu with the arrow keys. If the widget does not accept \fCArrowUp\fR and \fCArrowDown\fR in its key event handler, the focus will move back to the menu when the respective arrow key is hit one more time. This works with a QLineEdit, for example. If the widget accepts the arrow key itself, it must also provide the possibility to put the focus back on the menu again by calling TQWidget::focusNextPrevChild(). Futhermore, if the embedded widget closes the menu when the user made a selection, this can be done safely by calling:
Sets the label to \fIlabel\fR. The progress dialog resizes to fit. The label becomes owned by the progress dialog and will be deleted when necessary, so do not pass the address of an object on the stack.
@ -336,17 +336,17 @@ You can go on to add arbitrary child widgets to the single child in the scrollvi
.PP
.nf
.br
QLabel* child1 = new QLabel("CHILD", big_box);
TQLabel* child1 = new TQLabel("CHILD", big_box);
.br
QLabel* child2 = new QLabel("CHILD", big_box);
TQLabel* child2 = new TQLabel("CHILD", big_box);
.br
QLabel* child3 = new QLabel("CHILD", big_box);
TQLabel* child3 = new TQLabel("CHILD", big_box);
.br
...
.br
.fi
.PP
Here the QScrollView has four children: the viewport(), the verticalScrollBar(), the horizontalScrollBar() and a small cornerWidget(). The viewport() has one child: the big QVBox. The QVBox has the three QLabel objects as child widgets. When the view is scrolled, the QVBox is moved; its children move with it as child widgets normally do.
Here the QScrollView has four children: the viewport(), the verticalScrollBar(), the horizontalScrollBar() and a small cornerWidget(). The viewport() has one child: the big QVBox. The QVBox has the three TQLabel objects as child widgets. When the view is scrolled, the QVBox is moved; its children move with it as child widgets normally do.
.SH "Using a Very Big View with Some Widgets"
<center>
.ce 1
@ -360,20 +360,20 @@ The second usage of QScrollView (depicted above) is appropriate when few, if any
.br
QScrollView* sv = new QScrollView(...);
.br
QLabel* child1 = new QLabel("CHILD", sv->viewport());
TQLabel* child1 = new TQLabel("CHILD", sv->viewport());
.br
sv->addChild(child1);
.br
QLabel* child2 = new QLabel("CHILD", sv->viewport());
TQLabel* child2 = new TQLabel("CHILD", sv->viewport());
.br
sv->addChild(child2);
.br
QLabel* child3 = new QLabel("CHILD", sv->viewport());
TQLabel* child3 = new TQLabel("CHILD", sv->viewport());
.br
sv->addChild(child3);
.br
.fi
Here, the QScrollView has the same four children: the viewport(), the verticalScrollBar(), the horizontalScrollBar() and a small cornerWidget(). The viewport() has the three QLabel objects as child widgets. When the view is scrolled, the scrollview moves the child widgets individually.
Here, the QScrollView has the same four children: the viewport(), the verticalScrollBar(), the horizontalScrollBar() and a small cornerWidget(). The viewport() has the three TQLabel objects as child widgets. When the view is scrolled, the scrollview moves the child widgets individually.
.SH "Using a Very Big View with Many Widgets"
<center>
.ce 1
@ -389,15 +389,15 @@ The final usage of QScrollView (depicted above) is appropriate when many widgets
.br
sv->enableClipper(TRUE);
.br
QLabel* child1 = new QLabel("CHILD", sv->viewport());
TQLabel* child1 = new TQLabel("CHILD", sv->viewport());
.br
sv->addChild(child1);
.br
QLabel* child2 = new QLabel("CHILD", sv->viewport());
TQLabel* child2 = new TQLabel("CHILD", sv->viewport());
.br
sv->addChild(child2);
.br
QLabel* child3 = new QLabel("CHILD", sv->viewport());
TQLabel* child3 = new TQLabel("CHILD", sv->viewport());
@ -60,77 +60,77 @@ QSimpleRichText \- Small displayable piece of rich text
.br
.in -1c
.SH DESCRIPTION
The QSimpleRichText class provides a small displayable piece of rich text.
The TQSimpleRichText class provides a small displayable piece of rich text.
.PP
This class encapsulates simple rich text usage in which a string is interpreted as rich text and can be drawn. This is particularly useful if you want to display some rich text in a custom widget. A TQStyleSheet is needed to interpret the tags and format the rich text. TQt provides a default HTML-like style sheet, but you may define custom style sheets.
.PP
Once created, the rich text object can be queried for its width(), height(), and the actual width used (see widthUsed()). Most importantly, it can be drawn on any given TQPainter with draw(). QSimpleRichText can also be used to implement hypertext or active text facilities by using anchorAt(). A hit test through inText() makes it possible to use simple rich text for text objects in editable drawing canvases.
Once created, the rich text object can be queried for its width(), height(), and the actual width used (see widthUsed()). Most importantly, it can be drawn on any given TQPainter with draw(). TQSimpleRichText can also be used to implement hypertext or active text facilities by using anchorAt(). A hit test through inText() makes it possible to use simple rich text for text objects in editable drawing canvases.
.PP
Once constructed from a string the contents cannot be changed, only resized. If the contents change, just throw the rich text object away and make a new one with the new contents.
.PP
For large documents use TQTextEdit or TQTextBrowser. For very small items of rich text you can use a QLabel.
For large documents use TQTextEdit or TQTextBrowser. For very small items of rich text you can use a TQLabel.
.PP
If you are using QSimpleRichText to print in high resolution you should call setWidth(TQPainter, int) so that the content will be laid out properly on the page.
If you are using TQSimpleRichText to print in high resolution you should call setWidth(TQPainter, int) so that the content will be laid out properly on the page.
Constructs a TQSimpleRichText from the rich text string \fItext\fR and the font \fIfnt\fR.
.PP
The font is used as a basis for the text rendering. When using rich text rendering on a widget \fIw\fR, you would normally specify the widget's font, for example:
\fIcontext\fR is the optional context of the rich text object. This becomes important if \fItext\fR contains relative references, for example within image tags. QSimpleRichText always uses the default mime source factory (see TQMimeSourceFactory::defaultFactory()) to resolve those references. The context will then be used to calculate the absolute path. See TQMimeSourceFactory::makeAbsolute() for details.
\fIcontext\fR is the optional context of the rich text object. This becomes important if \fItext\fR contains relative references, for example within image tags. TQSimpleRichText always uses the default mime source factory (see TQMimeSourceFactory::defaultFactory()) to resolve those references. The context will then be used to calculate the absolute path. See TQMimeSourceFactory::makeAbsolute() for details.
.PP
The \fIsheet\fR is an optional style sheet. If it is 0, the default style sheet will be used (see TQStyleSheet::defaultSheet()).
Constructs a TQSimpleRichText from the rich text string \fItext\fR and the font \fIfnt\fR.
.PP
This is a slightly more complex constructor for QSimpleRichText that takes an additional mime source factory \fIfactory\fR, a page break parameter \fIpageBreak\fR and a bool \fIlinkUnderline\fR. \fIlinkColor\fR is only provided for compatibility, but has no effect, as TQColorGroup's TQColorGroup::link() color is used now.
This is a slightly more complex constructor for TQSimpleRichText that takes an additional mime source factory \fIfactory\fR, a page break parameter \fIpageBreak\fR and a bool \fIlinkUnderline\fR. \fIlinkColor\fR is only provided for compatibility, but has no effect, as TQColorGroup's TQColorGroup::link() color is used now.
.PP
\fIcontext\fR is the optional context of the rich text object. This becomes important if \fItext\fR contains relative references, for example within image tags. QSimpleRichText always uses the default mime source factory (see TQMimeSourceFactory::defaultFactory()) to resolve those references. The context will then be used to calculate the absolute path. See TQMimeSourceFactory::makeAbsolute() for details.
\fIcontext\fR is the optional context of the rich text object. This becomes important if \fItext\fR contains relative references, for example within image tags. TQSimpleRichText always uses the default mime source factory (see TQMimeSourceFactory::defaultFactory()) to resolve those references. The context will then be used to calculate the absolute path. See TQMimeSourceFactory::makeAbsolute() for details.
.PP
The \fIsheet\fR is an optional style sheet. If it is 0, the default style sheet will be used (see TQStyleSheet::defaultSheet()).
.PP
This constructor is useful for creating a QSimpleRichText object suitable for printing. Set \fIpageBreak\fR to be the height of the contents area of the pages.
.SH "QSimpleRichText::~QSimpleRichText ()"
This constructor is useful for creating a TQSimpleRichText object suitable for printing. Set \fIpageBreak\fR to be the height of the contents area of the pages.
.SH "TQSimpleRichText::~TQSimpleRichText ()"
Destroys the rich text object, freeing memory.
.SH "void QSimpleRichText::adjustSize ()"
.SH "void TQSimpleRichText::adjustSize ()"
Adjusts the richt text object to a reasonable size.
Returns the anchor at the requested position, \fIpos\fR. An empty string is returned if no anchor is specified for this position.
.SH "TQString QSimpleRichText::context () const"
.SH "TQString TQSimpleRichText::context () const"
Returns the context of the rich text object. If no context has been specified in the constructor, a null string is returned. The context is the path to use to look up relative links, such as image tags and anchor references.
.SH "void QSimpleRichText::draw ( TQPainter * p, int x, int y, const TQRect & clipRect, const TQColorGroup & cg, const TQBrush * paper = 0 ) const"
.SH "void TQSimpleRichText::draw ( TQPainter * p, int x, int y, const TQRect & clipRect, const TQColorGroup & cg, const TQBrush * paper = 0 ) const"
Draws the formatted text with painter \fIp\fR, at position (\fIx\fR, \fIy\fR), clipped to \fIclipRect\fR. The clipping rectangle is given in the rich text object's coordinates translated by (\fIx\fR, \fIy\fR). Passing an null rectangle results in no clipping. Colors from the color group \fIcg\fR are used as needed, and if not 0, \fI*paper\fR is used as the background brush.
.PP
Note that the display code is highly optimized to reduce flicker, so passing a brush for \fIpaper\fR is preferable to simply clearing the area to be painted and then calling this without a brush.
.PP
Examples:
.)l action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, and mdi/application.cpp.
.SH "void QSimpleRichText::draw ( TQPainter * p, int x, int y, const TQRegion & clipRegion, const TQColorGroup & cg, const TQBrush * paper = 0 ) const"
.SH "void TQSimpleRichText::draw ( TQPainter * p, int x, int y, const TQRegion & clipRegion, const TQColorGroup & cg, const TQBrush * paper = 0 ) const"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Use the version with clipRect instead. The region version has problems with larger documents on some platforms (on X11 regions internally are represented with 16bit coordinates).
.SH "int QSimpleRichText::height () const"
.SH "int TQSimpleRichText::height () const"
Returns the height of the rich text object in pixels.
.PP
See also setWidth().
.PP
Examples:
.)l action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, and mdi/application.cpp.
Returns TRUE if \fIpos\fR is within a text line of the rich text object; otherwise returns FALSE.
.SH "void QSimpleRichText::setDefaultFont ( const TQFont & f )"
.SH "void TQSimpleRichText::setDefaultFont ( const TQFont & f )"
Sets the default font for the rich text object to \fIf\fR
.SH "void QSimpleRichText::setWidth ( TQPainter * p, int w )"
.SH "void TQSimpleRichText::setWidth ( TQPainter * p, int w )"
Sets the width of the rich text object to \fIw\fR pixels, recalculating the layout as if it were to be drawn with painter \fIp\fR.
.PP
Passing a painter is useful when you intend drawing on devices other than the screen, for example a TQPrinter.
@ -139,17 +139,17 @@ See also height() and adjustSize().
.PP
Examples:
.)l action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, and mdi/application.cpp.
.SH "void QSimpleRichText::setWidth ( int w )"
.SH "void TQSimpleRichText::setWidth ( int w )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
Sets the width of the rich text object to \fIw\fR pixels.
.PP
See also height() and adjustSize().
.SH "int QSimpleRichText::width () const"
.SH "int TQSimpleRichText::width () const"
Returns the set width of the rich text object in pixels.
.PP
See also widthUsed().
.SH "int QSimpleRichText::widthUsed () const"
.SH "int TQSimpleRichText::widthUsed () const"
Returns the width in pixels that is actually used by the rich text object. This can be smaller or wider than the set width.
.PP
It may be wider, for example, if the text contains images or non-breakable words that are already wider than the available space. It's smaller when the object only consists of lines that do not fill the width completely.
@ -157,7 +157,7 @@ It may be wider, for example, if the text contains images or non-breakable words
@ -132,7 +132,7 @@ This is the constructor normally used to return a value in the overridden TQWidg
.PP
It constructs a TQSizePolicy with independent horizontal and vertical sizing types, \fIhor\fR and \fIver\fR respectively. These sizing types affect how the widget is treated by the layout engine.
.PP
If \fIhfw\fR is TRUE, the preferred height of the widget is dependent on the width of the widget (for example, a QLabel with line wrapping).
If \fIhfw\fR is TRUE, the preferred height of the widget is dependent on the width of the widget (for example, a TQLabel with line wrapping).
.PP
See also horData(), verData(), and hasHeightForWidth().
@ -100,7 +100,7 @@ To display a \fItemporary\fR message, call message() (perhaps by connecting a su
.br
.fi
.PP
\fINormal\fR and \fIPermanent\fR messages are displayed by creating a small widget and then adding it to the status bar with addWidget(). Widgets like QLabel, QProgressBar or even TQToolButton are useful for adding to status bars. removeWidget() is used to remove widgets.
\fINormal\fR and \fIPermanent\fR messages are displayed by creating a small widget and then adding it to the status bar with addWidget(). Widgets like TQLabel, QProgressBar or even TQToolButton are useful for adding to status bars. removeWidget() is used to remove widgets.
.PP
.nf
.br
@ -117,7 +117,7 @@ By default TQStatusBar provides a TQSizeGrip in the lower-right corner. You can
.ce 1
.B "[Image Omitted]"
.PP
See also TQToolBar, TQMainWindow, QLabel, GUI Design Handbook: Status Bar, Main Window and Related Classes, and Help System.
See also TQToolBar, TQMainWindow, TQLabel, GUI Design Handbook: Status Bar, Main Window and Related Classes, and Help System.
@ -400,10 +400,10 @@ All the functions in this class are reentrant when TQt is built with thread supp
.BI "TQChar \fBoperator[]\fR ( int i ) const"
.br
.ti -1c
.BI "QCharRef \fBat\fR ( uint i )"
.BI "TQCharRef \fBat\fR ( uint i )"
.br
.ti -1c
.BI "QCharRef \fBoperator[]\fR ( int i )"
.BI "TQCharRef \fBoperator[]\fR ( int i )"
.br
.ti -1c
.BI "TQChar \fBconstref\fR ( uint i ) const"
@ -655,7 +655,7 @@ The 'copying' of input to output is almost as fast as copying a pointer because
.PP
If you wish to create a deep copy of a TQString without losing any Unicode information then you should use TQDeepCopy.
.PP
See also TQChar, TQCString, TQByteArray, QConstString, Implicitly and Explicitly Shared Classes, Text Related Classes, and Non-GUI Classes.
See also TQChar, TQCString, TQByteArray, TQConstString, Implicitly and Explicitly Shared Classes, Text Related Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "TQString::SectionFlags"
.TP
@ -780,7 +780,7 @@ The \fIfieldWidth\fR value specifies the minimum amount of space that \fIa\fR is
.PP
\fIa\fR is expressed in base \fIbase\fR, which is 10 by default and must be between 2 and 36.
.PP
The '%' can be followed by an 'L', in which case the sequence is replaced with a localized representation of \fIa\fR. The conversion uses the default locale. The default locale is determined from the system's locale settings at application startup. It can be changed using QLocale::setDefault(). The 'L' flag is ignored if \fIbase\fR is not 10.
The '%' can be followed by an 'L', in which case the sequence is replaced with a localized representation of \fIa\fR. The conversion uses the default locale. The default locale is determined from the system's locale settings at application startup. It can be changed using TQLocale::setDefault(). The 'L' flag is ignored if \fIbase\fR is not 10.
.PP
.nf
.br
@ -793,7 +793,7 @@ The '%' can be followed by an 'L', in which case the sequence is replaced with a
@ -916,7 +916,7 @@ Returns the character at index \fIi\fR, or 0 if \fIi\fR is beyond the length of
.fi
.PP
If the TQString is not const (i.e. const TQString) or const& (i.e. const TQString &), then the non-const overload of at() will be used instead.
.SH "QCharRef TQString::at ( uint i )"
.SH "TQCharRef TQString::at ( uint i )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
The function returns a reference to the character at index \fIi\fR. The resulting reference can then be assigned to, or used immediately, but it will become invalid once further modifications are made to the original string.
@ -1553,14 +1553,14 @@ Sets the string to contain just the single character \fIc\fR.
Returns the character at index \fIi\fR, or TQChar::null if \fIi\fR is beyond the length of the string.
.PP
If the TQString is not const (i.e., const TQString) or const& (i.e., const TQString&), then the non-const overload of operator[] will be used instead.
.SH "QCharRef TQString::operator[] ( int i )"
.SH "TQCharRef TQString::operator[] ( int i )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
The function returns a reference to the character at index \fIi\fR. The resulting reference can then be assigned to, or used immediately, but it will become invalid once further modifications are made to the original string.
.PP
If \fIi\fR is beyond the length of the string then the string is expanded with TQChar::nulls, so that the QCharRef references a valid (null) character in the string.
If \fIi\fR is beyond the length of the string then the string is expanded with TQChar::nulls, so that the TQCharRef references a valid (null) character in the string.
.PP
The QCharRef internal class can be used much like a constant TQChar, but if you assign to it, you change the original string (which will detach itself because of TQString's copy-on-write semantics). You will get compilation errors if you try to use the result as anything but a TQChar.
The TQCharRef internal class can be used much like a constant TQChar, but if you assign to it, you change the original string (which will detach itself because of TQString's copy-on-write semantics). You will get compilation errors if you try to use the result as anything but a TQChar.
.SH "TQString & TQString::prepend ( const TQString & s )"
Inserts \fIs\fR at the beginning of the string and returns a reference to the string.
.PP
@ -2147,7 +2147,7 @@ toULongLong()
.TP
toFloat()
.TP
toDouble() can handle numbers represented in various locales. These representations may use different characters for the decimal point, thousands group sepearator and even individual digits. TQString's functions try to interpret the string according to the current locale. The current locale is determined from the system at application startup and can be changed by calling QLocale::setDefault(). If the string cannot be interpreted according to the current locale, this function falls back on the "C" locale.
toDouble() can handle numbers represented in various locales. These representations may use different characters for the decimal point, thousands group sepearator and even individual digits. TQString's functions try to interpret the string according to the current locale. The current locale is determined from the system at application startup and can be changed by calling TQLocale::setDefault(). If the string cannot be interpreted according to the current locale, this function falls back on the "C" locale.
.PP
.nf
.br
@ -2156,14 +2156,14 @@ toDouble() can handle numbers represented in various locales. These representati
double d;
.br
.br
QLocale::setDefault(QLocale::C);
TQLocale::setDefault(TQLocale::C);
.br
d = TQString( "1234,56" ).toDouble(&ok); // ok == false
.br
d = TQString( "1234.56" ).toDouble(&ok); // ok == true, d == 1234.56
.br
.br
QLocale::setDefault(QLocale::German);
TQLocale::setDefault(TQLocale::German);
.br
d = TQString( "1234,56" ).toDouble(&ok); // ok == true, d == 1234.56
.br
@ -2171,13 +2171,13 @@ toDouble() can handle numbers represented in various locales. These representati
.br
.fi
.PP
Due to the ambiguity between the decimal point and thousands group separator in various locales, these functions do not handle thousands group separators. If you need to convert such numbers, use the corresponding function in QLocale.
Due to the ambiguity between the decimal point and thousands group separator in various locales, these functions do not handle thousands group separators. If you need to convert such numbers, use the corresponding function in TQLocale.
.PP
.nf
.br
bool ok;
.br
QLocale::setDefault(QLocale::C);
TQLocale::setDefault(TQLocale::C);
.br
double d = TQString( "1,234,567.89" ).toDouble(&ok); // ok == false
.br
@ -2185,7 +2185,7 @@ Due to the ambiguity between the decimal point and thousands group separator in
.PP
\fBWarning:\fR If the string contains trailing whitespace this function will fail, and set \fI*ok\fR to false if \fIok\fR is not 0. Leading whitespace is ignored.
.PP
See also number(), QLocale::setDefault(), QLocale::toDouble(), and stripWhiteSpace().
See also number(), TQLocale::setDefault(), TQLocale::toDouble(), and stripWhiteSpace().
The TQStyleSheet class is a collection of styles for rich text rendering and a generator of tags.
.PP
By creating TQStyleSheetItem objects for a style sheet you build a definition of a set of tags. This definition will be used by the internal rich text rendering system to parse and display text documents to which the style sheet applies. Rich text is normally visualized in a TQTextEdit or a TQTextBrowser. However, QLabel, QWhatsThis and QMessageBox also support it, and other classes are likely to follow. With QSimpleRichText it is possible to use the rich text renderer for custom widgets as well.
By creating TQStyleSheetItem objects for a style sheet you build a definition of a set of tags. This definition will be used by the internal rich text rendering system to parse and display text documents to which the style sheet applies. Rich text is normally visualized in a TQTextEdit or a TQTextBrowser. However, TQLabel, TQWhatsThis and QMessageBox also support it, and other classes are likely to follow. With TQSimpleRichText it is possible to use the rich text renderer for custom widgets as well.
.PP
The default TQStyleSheet object has the following style bindings, sorted by structuring bindings, anchors, character style bindings (i.e. inline styles), special elements such as horizontal lines or images, and other tags. In addition, rich text supports simple HTML tables.
.PP
@ -152,7 +152,7 @@ See also escape().
Examples:
.)l action/application.cpp, application/application.cpp, and mdi/application.cpp.
Returns the application-wide default style sheet. This style sheet is used by rich text rendering classes such as QSimpleRichText, QWhatsThis and QMessageBox to define the rendering style and available tags within rich text documents. It also serves as the initial style sheet for the more complex render widgets, TQTextEdit and TQTextBrowser.
Returns the application-wide default style sheet. This style sheet is used by rich text rendering classes such as TQSimpleRichText, TQWhatsThis and QMessageBox to define the rendering style and available tags within rich text documents. It also serves as the initial style sheet for the more complex render widgets, TQTextEdit and TQTextBrowser.
Generates an internal object for the tag called \fIname\fR, given the attributes \fIattr\fR, and using additional information provided by the mime source factory \fIfactory\fR.
.PP
\fIcontext\fR is the optional context of the document, i.e. the path to look for relative links. This becomes important if the text contains relative references, for example within image tags. QSimpleRichText always uses the default mime source factory (see TQMimeSourceFactory::defaultFactory()) to resolve these references. The context will then be used to calculate the absolute path. See TQMimeSourceFactory::makeAbsolute() for details.
\fIcontext\fR is the optional context of the document, i.e. the path to look for relative links. This becomes important if the text contains relative references, for example within image tags. TQSimpleRichText always uses the default mime source factory (see TQMimeSourceFactory::defaultFactory()) to resolve these references. The context will then be used to calculate the absolute path. See TQMimeSourceFactory::makeAbsolute() for details.
.PP
\fIemptyTag\fR and \fIdoc\fR are for internal use only.
.BI "virtual int \fBhighlightParagraph\fR ( const TQString & text, int endStateOfLastPara ) = 0"
@ -44,27 +44,27 @@ Inherits Qt.
.br
.in -1c
.SH DESCRIPTION
The QSyntaxHighlighter class is a base class for implementing TQTextEdit syntax highlighters.
The TQSyntaxHighlighter class is a base class for implementing TQTextEdit syntax highlighters.
.PP
A syntax highligher automatically highlights parts of the text in a TQTextEdit. Syntax highlighters are often used when the user is entering text in a specific format (for example, source code) and help the user to read the text and identify syntax errors.
.PP
To provide your own syntax highlighting for TQTextEdit, you must subclass QSyntaxHighlighter and reimplement highlightParagraph().
To provide your own syntax highlighting for TQTextEdit, you must subclass TQSyntaxHighlighter and reimplement highlightParagraph().
.PP
When you create an instance of your QSyntaxHighlighter subclass, pass it the TQTextEdit that you want the syntax highlighting to be applied to. After this your highlightParagraph() function will be called automatically whenever necessary. Use your highlightParagraph() function to apply formatting (e.g. setting the font and color) to the text that is passed to it.
When you create an instance of your TQSyntaxHighlighter subclass, pass it the TQTextEdit that you want the syntax highlighting to be applied to. After this your highlightParagraph() function will be called automatically whenever necessary. Use your highlightParagraph() function to apply formatting (e.g. setting the font and color) to the text that is passed to it.
This function is called when necessary by the rich text engine, i.e. on paragraphs which have changed.
.PP
In your reimplementation you should parse the paragraph's \fItext\fR and call setFormat() as often as necessary to apply any font and color changes that you require. Your function must return a value which indicates the paragraph's end state: see below.
@ -80,22 +80,22 @@ The value you return is up to you. We recommend only returning 0 (to signify tha
To find out which paragraph is highlighted, call currentParagraph().
.PP
For example, if you're writing a simple C++ syntax highlighter, you might designate 1 to signify "in comment". For a paragraph that ended in the middle of a comment you'd return 1, and for other paragraphs you'd return 0. In your parsing code if \fIendStateOfLastPara\fR was 1, you would highlight the text as a C++ comment until you reached the closing \fC*\fR\fC/\fR.
.SH "void QSyntaxHighlighter::rehighlight ()"
.SH "void TQSyntaxHighlighter::rehighlight ()"
Redoes the highlighting of the whole document.
.SH "void QSyntaxHighlighter::setFormat ( int start, int count, const TQFont & font, const TQColor & color )"
.SH "void TQSyntaxHighlighter::setFormat ( int start, int count, const TQFont & font, const TQColor & color )"
This function is applied to the syntax highlighter's current paragraph (the text of which is passed to the highlightParagraph() function).
.PP
The specified \fIfont\fR and \fIcolor\fR are applied to the text from position \fIstart\fR for \fIcount\fR characters. (If \fIcount\fR is 0, nothing is done.)
.SH "void QSyntaxHighlighter::setFormat ( int start, int count, const TQColor & color )"
.SH "void TQSyntaxHighlighter::setFormat ( int start, int count, const TQColor & color )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.SH "void QSyntaxHighlighter::setFormat ( int start, int count, const TQFont & font )"
.SH "void TQSyntaxHighlighter::setFormat ( int start, int count, const TQFont & font )"
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
@ -1210,7 +1210,7 @@ You can use as many modifier flags as you want, except that SingleLine and WordB
.PP
Flags that are inappropriate for a given use (e.g. ShowPrefix to QGridLayout::addWidget()) are generally ignored.
.SH "TQt::TextFormat"
This enum is used in widgets that can display both plain text and rich text, e.g. QLabel. It is used for deciding whether a text string should be interpreted as one or the other. This is normally done by passing one of the enum values to a setTextFormat() function.
This enum is used in widgets that can display both plain text and rich text, e.g. TQLabel. It is used for deciding whether a text string should be interpreted as one or the other. This is normally done by passing one of the enum values to a setTextFormat() function.
.TP
\fCQt::PlainText\fR - The text string is interpreted as a plain text string.
@ -108,7 +108,7 @@ This is to ensure that the factory is able to resolve the document names.
.PP
TQTextBrowser interprets the tags it processes in accordance with the default style sheet. Change the style sheet with setStyleSheet(); see TQStyleSheet for details.
.PP
If you want to provide your users with editable rich text use TQTextEdit. If you want a text browser without hypertext navigation use TQTextEdit, and use TQTextEdit::setReadOnly() to disable editing. If you just need to display a small piece of rich text use QSimpleRichText or QLabel.
If you want to provide your users with editable rich text use TQTextEdit. If you want a text browser without hypertext navigation use TQTextEdit, and use TQTextEdit::setReadOnly() to disable editing. If you just need to display a small piece of rich text use TQSimpleRichText or TQLabel.
@ -539,7 +539,7 @@ l - l. Mode Command Notes Plain Text Editor setTextFormat(PlainText) Set text wi
.PP
<sup>1.</sup><small>A more complete API that supports setting margins, images, etc., is planned for a later TQt release.</small>
.PP
TQTextEdit can be used as a syntax highlighting editor when used in conjunction with QSyntaxHighlighter.
TQTextEdit can be used as a syntax highlighting editor when used in conjunction with TQSyntaxHighlighter.
.PP
We recommend that you always call setTextFormat() to set the mode you want to use. If you use AutoText then setText() and append() will try to determine whether the text they are given is plain text or rich text. If you use RichText then setText() and append() will assume that the text they are given is rich text. insert() simply inserts the text it is given.
.PP
@ -553,7 +553,7 @@ The text edit documentation uses the following concepts:
.PP
TQTextEdit can display images (using TQMimeSourceFactory), lists and tables. If the text is too large to view within the text edit's viewport, scrollbars will appear. The text edit can load both plain text and HTML files (a subset of HTML 3.2 and 4). The rendering style and the set of valid tags are defined by a styleSheet(). Custom tags can be created and placed in a custom style sheet. Change the style sheet with setStyleSheet(); see TQStyleSheet for details. The images identified by image tags are displayed if they can be interpreted using the text edit's TQMimeSourceFactory; see setMimeSourceFactory().
.PP
If you want a text browser with more navigation use TQTextBrowser. If you just need to display a small piece of rich text use QLabel or QSimpleRichText.
If you want a text browser with more navigation use TQTextBrowser. If you just need to display a small piece of rich text use TQLabel or TQSimpleRichText.
.PP
If you create a new TQTextEdit, and want to allow the user to edit rich text, call setTextFormat(TQt::RichText) to ensure that the text is treated as rich text. (Rich text uses HTML tags to set text formatting attributes. See TQStyleSheet for information on the HTML tags that are supported.). If you don't call setTextFormat() explicitly the text edit will guess from the text itself whether it is rich text or plain text. This means that if the text looks like HTML or XML it will probably be interpreted as rich text, so you should call setTextFormat(TQt::PlainText) to preserve such text.
.PP
@ -1215,8 +1215,8 @@ Examples:
TQTextEdit is optimized for large amounts text. One of its optimizations is to format only the visible text, formatting the rest on demand, e.g. as the user scrolls, so you don't usually need to call this function.
.PP
In some situations you may want to force the whole text to be formatted. For example, if after calling setText(), you wanted to know the height of the document (using contentsHeight()), you would call this function first.
Constructs a tool tip object. This is only necessary if you need tool tips on regions that can move within the widget (most often because the widget's contents can scroll).
The QWhatsThis class provides a simple description of any widget, i.e. answering the question "What's this?".
The TQWhatsThis class provides a simple description of any widget, i.e. answering the question "What's this?".
.PP
.PP"
What's this?" help is part of an application's online help system that provides users with information about functionality, usage, background etc., in various levels of detail from short tool tips to full text browsing help windows.
.PP
QWhatsThis provides a single window with an explanatory text that pops up when the user asks "What's this?". The default way to do this is to focus the relevant widget and press Shift+F1. The help text appears immediately; it goes away as soon as the user does something else.
TQWhatsThis provides a single window with an explanatory text that pops up when the user asks "What's this?". The default way to do this is to focus the relevant widget and press Shift+F1. The help text appears immediately; it goes away as soon as the user does something else.
.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 QWhatsThis::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 QAccel::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
@ -89,7 +89,7 @@ The text can be either rich text or plain text. If you specify a rich text forma
fileOpenAction->setWhatsThis( fileOpenText );
.fi
.PP
An alternative way to enter "What's this?" mode is to use the ready-made tool bar tool button from QWhatsThis::whatsThisButton(). By invoking this context help button (in the picture below the first one from the right) the user switches into "What's this?" mode. If they now click on a widget the appropriate help text is shown. The mode is left when help is given or when the user presses Esc.
An alternative way to enter "What's this?" mode is to use the ready-made tool bar tool button from TQWhatsThis::whatsThisButton(). By invoking this context help button (in the picture below the first one from the right) the user switches into "What's this?" mode. If they now click on a widget the appropriate help text is shown. The mode is left when help is given or when the user presses Esc.
.PP
<center>
.ce 1
@ -99,21 +99,21 @@ An alternative way to enter "What's this?" mode is to use the ready-made tool ba
.PP
If you are using TQMainWindow you can also use the TQMainWindow::whatsThis() slot to invoke the mode from a menu item.
.PP
For more control you can create a dedicated QWhatsThis object for a special widget. By subclassing and reimplementing QWhatsThis::text() it is possible to have different help texts, depending on the position of the mouse click. By reimplementing QWhatsThis::clicked() it is possible to have hyperlinks inside the help texts.
For more control you can create a dedicated TQWhatsThis object for a special widget. By subclassing and reimplementing TQWhatsThis::text() it is possible to have different help texts, depending on the position of the mouse click. By reimplementing TQWhatsThis::clicked() it is possible to have hyperlinks inside the help texts.
.PP
If you wish to control the "What's this?" behavior of a widget manually see TQWidget::customWhatsThis().
.PP
The What's This object can be removed using QWhatsThis::remove(), although this is rarely necessary because it is automatically removed when the widget is destroyed.
The What's This object can be removed using TQWhatsThis::remove(), although this is rarely necessary because it is automatically removed when the widget is destroyed.
Constructs a dynamic "What's this?" object for \fIwidget\fR. The object is deleted when the \fIwidget\fR is destroyed.
.PP
When the widget is queried by the user the text() function of this QWhatsThis will be called to provide the appropriate text, rather than using the text assigned by add().
.SH "QWhatsThis::~QWhatsThis ()\fC [virtual]\fR"
When the widget is queried by the user the text() function of this TQWhatsThis will be called to provide the appropriate text, rather than using the text assigned by add().
Adds \fItext\fR as "What's this" help for \fIwidget\fR. If the text is rich text formatted (i.e. it contains markup) it will be rendered with the default stylesheet TQStyleSheet::defaultSheet().
.PP
The text is destroyed if the widget is later destroyed, so it need not be explicitly removed.
@ -122,19 +122,19 @@ See also remove().
.PP
Examples:
.)l application/application.cpp, helpsystem/mainwindow.cpp, and mdi/application.cpp.
This virtual function is called when the user clicks inside the" What's this?" window. \fIhref\fR is the link the user clicked on, or TQString::null if there was no link.
.PP
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 QWhatsThis object, this object will receive clicked() messages when the user clicks on hyperlinks inside the help text.
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.
Enters "What's this?" mode and returns immediately.
.PP
Qt will install a special cursor and take over mouse input until the user clicks somewhere. It then shows any help available and ends "What's this?" mode. Finally, TQt removes the special cursor and help window and then restores ordinary event processing, at which point the left mouse button is no longer pressed.
@ -142,47 +142,47 @@ Qt will install a special cursor and take over mouse input until the user clicks
The user can also use the Esc key to leave "What's this?" mode.
.PP
See also inWhatsThisMode() 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.
.PP
If \fItext\fR is not TQString::null, a "What's this?" help window is displayed at the global screen position \fIpos\fR. If widget \fIw\fR is not 0 and has its own dedicated QWhatsThis object, this object will receive clicked() messages when the user clicks on hyperlinks inside the help text.
If \fItext\fR is not TQString::null, a "What's this?" help window is displayed at the global screen position \fIpos\fR. 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.
.PP
See also inWhatsThisMode(), enterWhatsThisMode(), and QWhatsThis::clicked().
This virtual function returns the text for position \fIp\fR in the widget that this "What's this?" object documents. If there is no" What's this?" text for the position, TQString::null is returned.
.PP
The default implementation returns TQString::null.
Returns the what's this text for widget \fIw\fR or TQString::null if there is no "What's this?" help for the widget. \fIpos\fR contains the mouse position; this is useful, for example, if you've subclassed to make the text that is displayed position dependent.
.PP
If \fIincludeParents\fR is TRUE, parent widgets are taken into consideration as well when looking for what's this help text.
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
@ -2646,11 +2646,11 @@ This property holds whether the widget wants to handle What's This help manually
.PP
The default implementation of customWhatsThis() returns FALSE, which means the widget will not receive any events in Whats This mode.
.PP
The widget may leave What's This mode by calling QWhatsThis::leaveWhatsThisMode(), with or without actually displaying any help text.
The widget may leave What's This mode by calling TQWhatsThis::leaveWhatsThisMode(), with or without actually displaying any help text.
.PP
You can also reimplement customWhatsThis() if your widget is a" passive interactor" supposed to work under all circumstances. Simply don't call QWhatsThis::leaveWhatsThisMode() in that case.
You can also reimplement customWhatsThis() if your widget is a" passive interactor" supposed to work under all circumstances. Simply don't call TQWhatsThis::leaveWhatsThisMode() in that case.
.PP
See also QWhatsThis::inWhatsThisMode() and QWhatsThis::leaveWhatsThisMode().
See also TQWhatsThis::inWhatsThisMode() and TQWhatsThis::leaveWhatsThisMode().
<p>If <em>text</em> is interpreted as a plain text, and a buddy has been set,
the buddy accelerator key is updated from the new text.
<p>The label resizes itself if auto-resizing is enabled.
<p>Note that Qlabel is well suited to display small rich text documents
<p>Note that TQLabel is well suited to display small rich text documents
only. For large documents, use <ahref="tqtextview.html">TQTextView</a> instead. It will flicker
less on resize and can also provide a scrollbar if necessary.
<p>See also <ahref="#72cf09">text</a>(), <ahref="#5de3f9">setTextFormat</a>(), <ahref="#191701">setBuddy</a>() and <ahref="#1f406e">setAlignment</a>().
