You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
495 lines
26 KiB
495 lines
26 KiB
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/examples/helpsystem/helpsystem.doc:1 -->
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
|
<title>Helpsystem</title>
|
|
<style type="text/css"><!--
|
|
fn { margin-left: 1cm; text-indent: -1cm; }
|
|
a:link { color: #004faf; text-decoration: none }
|
|
a:visited { color: #672967; text-decoration: none }
|
|
body { background: #ffffff; color: black; }
|
|
--></style>
|
|
</head>
|
|
<body>
|
|
|
|
<table border="0" cellpadding="0" cellspacing="0" width="100%">
|
|
<tr bgcolor="#E5E5E5">
|
|
<td valign=center>
|
|
<a href="index.html">
|
|
<font color="#004faf">Home</font></a>
|
|
| <a href="classes.html">
|
|
<font color="#004faf">All Classes</font></a>
|
|
| <a href="mainclasses.html">
|
|
<font color="#004faf">Main Classes</font></a>
|
|
| <a href="annotated.html">
|
|
<font color="#004faf">Annotated</font></a>
|
|
| <a href="groups.html">
|
|
<font color="#004faf">Grouped Classes</font></a>
|
|
| <a href="functions.html">
|
|
<font color="#004faf">Functions</font></a>
|
|
</td>
|
|
<td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Helpsystem</h1>
|
|
|
|
|
|
|
|
<p>
|
|
This example demonstrates the different TQt classes
|
|
that can be used to provide context sensitive help
|
|
in an application.
|
|
<p> It uses <a href="tqtooltip.html">TQToolTip</a> and <a href="ntqwhatsthis.html">TQWhatsThis</a> to provide both static and
|
|
dynamic balloon help for the widgets in the application, and
|
|
<a href="tqtooltipgroup.html">TQToolTipGroup</a> to display extended information for each tooltip
|
|
in the statusbar. <a href="ntqassistantclient.html">TQAssistantClient</a> is used to display help
|
|
pages using TQt Assistant.
|
|
<p> The application has a user interface based on a
|
|
<a href="tqmainwindow.html">TQMainWindow</a> with a menubar, statusbar and a toolbar, and uses
|
|
a <a href="ntqtable.html">TQTable</a> as the central widget.
|
|
|
|
|
|
<pre> class HeaderToolTip : public <a href="tqtooltip.html">TQToolTip</a>
|
|
{
|
|
public:
|
|
HeaderToolTip( <a href="ntqheader.html">TQHeader</a> *header, TQToolTipGroup *group = 0 );
|
|
|
|
protected:
|
|
void maybeTip ( const <a href="ntqpoint.html">TQPoint</a> &p );
|
|
};
|
|
</pre>
|
|
<p> Two TQToolTip subclasses implement dynamic tooltips for
|
|
<a href="ntqheader.html">TQHeader</a> and TQTable by reimplementing maybeTip(). The
|
|
constructors differ from the <a href="tqtooltip.html">TQToolTip</a> constructor in having a
|
|
TQHeader and a TQTable respectively as the first parameter for
|
|
the constructor instead of a <a href="tqwidget.html">TQWidget</a>. This is because
|
|
we want to ensure that only headers and tables can be
|
|
passed as arguments. A <a href="tqtooltipgroup.html">TQToolTipGroup</a> can be provided as the
|
|
second argument to show tooltips in, for example a statusbar.
|
|
<p> <pre> class TableToolTip : public <a href="tqtooltip.html">TQToolTip</a>
|
|
{
|
|
public:
|
|
TableToolTip( <a href="ntqtable.html">TQTable</a>* table, TQToolTipGroup *group = 0 );
|
|
|
|
protected:
|
|
void maybeTip( const <a href="ntqpoint.html">TQPoint</a> &p );
|
|
|
|
private:
|
|
<a href="ntqtable.html">TQTable</a> *table;
|
|
};
|
|
</pre>
|
|
<p> The TableToolTip class keeps a reference to the <a href="ntqtable.html">TQTable</a>
|
|
as a member for easier access of the TQTable object later on.
|
|
<p>
|
|
|
|
<pre> HeaderToolTip::HeaderToolTip( <a href="ntqheader.html">TQHeader</a> *header, TQToolTipGroup *group )
|
|
: <a href="tqtooltip.html">TQToolTip</a>( header, group )
|
|
{
|
|
}
|
|
</pre>
|
|
<p> The HeaderToolTip constructor propagates the parameters
|
|
to the <a href="tqtooltip.html">TQToolTip</a> constructor.
|
|
<pre> void HeaderToolTip::<a href="tqtooltip.html#maybeTip">maybeTip</a> ( const <a href="ntqpoint.html">TQPoint</a>& p )
|
|
{
|
|
<a href="ntqheader.html">TQHeader</a> *header = (TQHeader*)<a href="tqtooltip.html#parentWidget">parentWidget</a>();
|
|
|
|
int section = 0;
|
|
|
|
<a name="x2676"></a> if ( header-><a href="ntqheader.html#orientation">orientation</a>() == Horizontal )
|
|
<a name="x2677"></a><a name="x2675"></a> section = header-><a href="ntqheader.html#sectionAt">sectionAt</a>( header-><a href="ntqheader.html#offset">offset</a>() + p.<a href="ntqpoint.html#x">x</a>() );
|
|
else
|
|
section = header-><a href="ntqheader.html#sectionAt">sectionAt</a>( header-><a href="ntqheader.html#offset">offset</a>() + p.<a href="ntqpoint.html#y">y</a>() );
|
|
|
|
<a name="x2674"></a> <a href="tqstring.html">TQString</a> tipString = header-><a href="ntqheader.html#label">label</a>( section );
|
|
<a name="x2678"></a> <a href="tqtooltip.html#tip">tip</a>( header-><a href="ntqheader.html#sectionRect">sectionRect</a>( section ), tipString, "This is a section in a header" );
|
|
}
|
|
</pre>
|
|
<p> The implementation of maybeTip() uses the <a href="ntqheader.html">TQHeader</a> API
|
|
to get the section at the requested position and uses
|
|
<a href="tqtooltip.html#tip">TQToolTip::tip</a>() to display the section's label in a
|
|
tooltip. The second string is used by <a href="tqtooltipgroup.html">TQToolTipGroup</a> and will
|
|
show up in the statusbar.
|
|
<p> <pre> TableToolTip::TableToolTip( <a href="ntqtable.html">TQTable</a> *tipTable, TQToolTipGroup *group )
|
|
<a name="x2683"></a>: <a href="tqtooltip.html">TQToolTip</a>( tipTable-><a href="ntqscrollview.html#viewport">viewport</a>(), group ), table( tipTable )
|
|
{
|
|
}
|
|
</pre>
|
|
<p> Since <a href="ntqtable.html">TQTable</a> is a <a href="ntqscrollview.html">TQScrollView</a> all user interaction
|
|
happens on TQTable's viewport() . The TableToolTip
|
|
constructor passes the viewport() and the tooltip
|
|
group to the <a href="tqtooltip.html">TQToolTip</a> constructor, and initializes the table
|
|
member with the TQTable pointer itself.
|
|
<pre> <a name="x2684"></a>void TableToolTip::<a href="tqtooltip.html#maybeTip">maybeTip</a> ( const <a href="ntqpoint.html">TQPoint</a> &p )
|
|
{
|
|
<a href="ntqpoint.html">TQPoint</a> cp = table->viewportToContents( p );
|
|
<a name="x2680"></a> int row = table->rowAt( cp.<a href="ntqpoint.html#y">y</a>() );
|
|
<a name="x2679"></a> int col = table->columnAt( cp.<a href="ntqpoint.html#x">x</a>() );
|
|
|
|
<a href="tqstring.html">TQString</a> tipString = table->text( row, col );
|
|
|
|
<a href="ntqrect.html">TQRect</a> cr = table->cellGeometry( row, col );
|
|
</pre>
|
|
<p> The implementation of maybeTip() uses the TQTable API
|
|
to get information about the cell at the requested position.
|
|
The <a href="ntqtable.html">TQTable</a> API expects contents coordinates, and since the
|
|
requested point is relative to the viewport we need to translate
|
|
the coordinates before we can use TQTable's functions.
|
|
<pre> <a name="x2682"></a><a name="x2681"></a> cr.<a href="ntqrect.html#moveTopLeft">moveTopLeft</a>( table->contentsToViewport( cr.<a href="ntqrect.html#topLeft">topLeft</a>() ) );
|
|
<a href="tqtooltip.html#tip">tip</a>( cr, tipString, "This is a cell in a table" );
|
|
}
|
|
</pre>
|
|
|
|
|
|
|
|
<p> We translate the cell's geometry back to viewport coordinates
|
|
so that the tooltip disappears when the mouse cursor leaves
|
|
the cell, and use <a href="tqtooltip.html#tip">TQToolTip::tip</a>() to display the cell's label
|
|
in a tooltip and to provide text for the <a href="tqtooltipgroup.html">TQToolTipGroup</a> as before.
|
|
<pre> class WhatsThis : public <a href="tqobject.html">TQObject</a>, public TQWhatsThis
|
|
{
|
|
<a href="metaobjects.html#TQ_OBJECT">TQ_OBJECT</a>
|
|
public:
|
|
WhatsThis( <a href="tqwidget.html">TQWidget</a> *w, TQWidget *watch = 0 );
|
|
|
|
bool clicked( const <a href="tqstring.html">TQString</a> &link );
|
|
<a href="tqwidget.html">TQWidget</a> *parentWidget() const;
|
|
|
|
signals:
|
|
void linkClicked( const <a href="tqstring.html">TQString</a> &link );
|
|
|
|
private:
|
|
<a href="tqwidget.html">TQWidget</a> *widget;
|
|
};
|
|
</pre>
|
|
|
|
|
|
|
|
<p> The WhatsThis class is a subclass of both <a href="tqobject.html">TQObject</a> and
|
|
<a href="ntqwhatsthis.html">TQWhatsThis</a> and serves as a base class for the HeaderWhatsThis
|
|
and TableWhatsThis classes. <a href="#footnote1"><sup>(1)</sup></a><a name="footnote-call1"></a> WhatsThis
|
|
reimplements clicked() which will be called when the user clicks
|
|
inside the "What's this?" window. It also declares a signal
|
|
linkClicked() which will be emitted when a hyperlink is clicked.
|
|
<pre> WhatsThis::WhatsThis( <a href="tqwidget.html">TQWidget</a> *w, TQWidget *watch )
|
|
: <a href="ntqwhatsthis.html">TQWhatsThis</a>( watch ? watch : w ), widget( w )
|
|
{
|
|
}
|
|
</pre>
|
|
<p> The WhatsThis constructor takes two parameters, the first is the
|
|
widget we want to provide WhatsThis for, and the second is the
|
|
one which receives the events. Normally this is the same widget,
|
|
but some widgets, like <a href="ntqtable.html">TQTable</a>, are more complex and have a
|
|
viewport() widget which receives the events. If such a widget
|
|
is passed to the constructor it will propagate the parameter to
|
|
the TQWhatsThis constructor and store the <a href="tqwidget.html">TQWidget</a> pointer itself
|
|
in it's member variable to allow easier use of the TQWidget API
|
|
later on.
|
|
<pre> bool WhatsThis::clicked( const <a href="tqstring.html">TQString</a> &link )
|
|
{
|
|
if ( !link.<a href="tqstring.html#isEmpty">isEmpty</a>() )
|
|
emit linkClicked( link );
|
|
|
|
return TRUE;
|
|
}
|
|
</pre>
|
|
|
|
|
|
|
|
<p> The implementation of clicked() emits the linkClicked() signal
|
|
if a hyperlink has been clicked.
|
|
<pre> class HeaderWhatsThis : public WhatsThis
|
|
{
|
|
public:
|
|
HeaderWhatsThis( <a href="ntqheader.html">TQHeader</a> *h );
|
|
|
|
<a href="tqstring.html">TQString</a> text( const <a href="ntqpoint.html">TQPoint</a> &p );
|
|
};
|
|
</pre>
|
|
<p> <pre> class TableWhatsThis : public WhatsThis
|
|
{
|
|
public:
|
|
TableWhatsThis( <a href="ntqtable.html">TQTable</a> *t );
|
|
|
|
<a href="tqstring.html">TQString</a> text( const <a href="ntqpoint.html">TQPoint</a> &p );
|
|
};
|
|
</pre>
|
|
<p>
|
|
|
|
|
|
|
|
<p> The HeaderWhatsThis and TableWhatsThis classes reimplement
|
|
text() to make it possible to return texts depending on the
|
|
mouse click's position. All the other functionality is
|
|
already provided by the generic WhatsThis base class. We ensure
|
|
type safety here in the same manner as in the tooltip classes.
|
|
<pre> HeaderWhatsThis::HeaderWhatsThis( <a href="ntqheader.html">TQHeader</a> *h )
|
|
: WhatsThis( h )
|
|
{
|
|
}
|
|
</pre>
|
|
<p> The HeaderWhatsThis constructor propagates the parameter to the
|
|
WhatsThis constructor.
|
|
<pre> TQString HeaderWhatsThis::text( const <a href="ntqpoint.html">TQPoint</a> &p )
|
|
{
|
|
<a href="ntqheader.html">TQHeader</a> *header = (TQHeader*)parentWidget();
|
|
|
|
<a href="tqstring.html">TQString</a> orient;
|
|
int section;
|
|
if ( header-><a href="ntqheader.html#orientation">orientation</a>() == TQObject::Horizontal ) {
|
|
orient = "horizontal";
|
|
section = header-><a href="ntqheader.html#sectionAt">sectionAt</a>( p.<a href="ntqpoint.html#x">x</a>() );
|
|
} else {
|
|
orient = "vertical";
|
|
section = header-><a href="ntqheader.html#sectionAt">sectionAt</a>( p.<a href="ntqpoint.html#y">y</a>() );
|
|
}
|
|
if( section == -1 )
|
|
return "This is empty space.";
|
|
<a href="tqstring.html">TQString</a> docsPath = TQDir("../../doc").absPath();
|
|
return TQString("This is section number %1 in the %2 <a href=%2/html/ntqheader.html>header</a>.").
|
|
arg(section + 1).
|
|
arg(orient).
|
|
arg(docsPath);
|
|
}
|
|
</pre>
|
|
<p> The implementation of text() uses the <a href="ntqheader.html">TQHeader</a> API to determine
|
|
whether we have a horizontal or a vertical header and returns
|
|
a string which states the header's orientation and section.
|
|
<a href="#footnote2"><sup>(2)</sup></a><a name="footnote-call2"></a>
|
|
<pre> TableWhatsThis::TableWhatsThis( <a href="ntqtable.html">TQTable</a> *t )
|
|
: WhatsThis( t, t-><a href="ntqscrollview.html#viewport">viewport</a>() )
|
|
{
|
|
}
|
|
</pre>
|
|
<p> Since <a href="ntqtable.html">TQTable</a> is a scrollview and has a viewport() which receives
|
|
the events, we propagate the table itself and the table's
|
|
viewport() to the WhatsThis constructor.
|
|
<pre> TQString TableWhatsThis::text( const <a href="ntqpoint.html">TQPoint</a> &p )
|
|
{
|
|
<a href="ntqtable.html">TQTable</a> *table = (TQTable*)parentWidget();
|
|
|
|
<a href="ntqpoint.html">TQPoint</a> cp = table-><a href="ntqscrollview.html#viewportToContents">viewportToContents</a>( p );
|
|
int row = table-><a href="ntqtable.html#rowAt">rowAt</a>( cp.<a href="ntqpoint.html#y">y</a>() );
|
|
int col = table-><a href="ntqtable.html#columnAt">columnAt</a>( cp.<a href="ntqpoint.html#x">x</a>() );
|
|
|
|
if ( row == -1 || col == -1 )
|
|
return "This is empty space.";
|
|
|
|
<a href="qtableitem.html">TQTableItem</a>* i = table-><a href="ntqtable.html#item">item</a>( row,col );
|
|
if ( !i )
|
|
return "This is an empty cell.";
|
|
|
|
<a href="tqstring.html">TQString</a> docsPath = TQDir("../../doc").absPath();
|
|
|
|
if ( TQTableItem::RTTI == i-><a href="qtableitem.html#rtti">rtti</a>() ) {
|
|
return TQString("This is a <a href=%1/html/qtableitem.html>TQTableItem</a>.").
|
|
arg(docsPath);
|
|
} else if ( TQComboTableItem::RTTI == i-><a href="qtableitem.html#rtti">rtti</a>() ) {
|
|
return TQString("This is a <a href=%1/html/qcombotableitem.html>TQComboTableItem</a>."
|
|
"<br>It can be used to provide multiple-choice items in a table.").
|
|
arg(docsPath);
|
|
} else if ( TQCheckTableItem::RTTI == i-><a href="qtableitem.html#rtti">rtti</a>() ) {
|
|
return TQString("This is a <a href=%1/html/qchecktableitem.html>TQCheckTableItem</a>."
|
|
"<br>It provide <a href=%1/html/ntqcheckbox.html>checkboxes</a> in tables.").
|
|
arg(docsPath).arg(docsPath);
|
|
}
|
|
return "This is a user defined table item.";
|
|
}
|
|
</pre>
|
|
<p> The implementation of text() uses the <a href="ntqtable.html">TQTable</a> API to get
|
|
information about the cell at the requested position.
|
|
The TQTable API expects contents coordinates, so we need to
|
|
translate the point as shown earlier for the tooltip classes.
|
|
We use the rtti() function to figure out the item's type
|
|
and return a string accordingly.
|
|
<p>
|
|
|
|
<pre> class MainWindow : public <a href="tqmainwindow.html">TQMainWindow</a>
|
|
{
|
|
TQ_OBJECT
|
|
public:
|
|
MainWindow();
|
|
~MainWindow();
|
|
|
|
public slots:
|
|
void assistantSlot();
|
|
|
|
private:
|
|
HeaderToolTip *horizontalTip;
|
|
HeaderToolTip *verticalTip;
|
|
TableToolTip *cellTip;
|
|
<a href="ntqassistantclient.html">TQAssistantClient</a> *assistant;
|
|
};
|
|
</pre>
|
|
<p> A <a href="tqmainwindow.html">TQMainWindow</a> is used to create a user interface that uses the
|
|
above classes in addition to TQt Assistant to provide context
|
|
sensitive help in the application.
|
|
<p> The MainWindow class declares a slot called assistantSlot()
|
|
which creates an instance of TQt Assistant when it is called.
|
|
The class keeps references to the tooltip classes as members
|
|
because they are not TQObjects and need to be deleted explicitly.
|
|
The class has a reference to <a href="ntqassistantclient.html">TQAssistantClient</a> as a
|
|
member as well, to allow easier access to TQt Assistant later on.
|
|
<p>
|
|
|
|
<pre> MainWindow::MainWindow()
|
|
{
|
|
<a href="tqmainwindow.html#statusBar">statusBar</a>();
|
|
assistant = new <a href="ntqassistantclient.html">TQAssistantClient</a>( TQDir("../../bin").absPath(), this );
|
|
</pre>
|
|
<p> The MainWindow constructor creates an instance of
|
|
TQAssistantClient using <a href="tqstring.html#TQString-null">TQString::null</a> as the first argument
|
|
so that the system path is used.
|
|
<pre> <a href="ntqtable.html">TQTable</a>* table = new <a href="ntqtable.html">TQTable</a>( 2, 3, this );
|
|
<a href="tqmainwindow.html#setCentralWidget">setCentralWidget</a>( table );
|
|
|
|
// populate table
|
|
<a href="tqstringlist.html">TQStringList</a> comboEntries;
|
|
comboEntries << "one" << "two" << "three" << "four";
|
|
<a href="qcombotableitem.html">TQComboTableItem</a>* comboItem1 = new <a href="qcombotableitem.html">TQComboTableItem</a>( table, comboEntries );
|
|
<a href="qcombotableitem.html">TQComboTableItem</a>* comboItem2 = new <a href="qcombotableitem.html">TQComboTableItem</a>( table, comboEntries );
|
|
<a href="qchecktableitem.html">TQCheckTableItem</a>* checkItem1 = new <a href="qchecktableitem.html">TQCheckTableItem</a>( table, "Check me" );
|
|
<a href="qchecktableitem.html">TQCheckTableItem</a>* checkItem2 = new <a href="qchecktableitem.html">TQCheckTableItem</a>( table, "Check me" );
|
|
|
|
<a name="x2691"></a> table-><a href="ntqtable.html#setItem">setItem</a>( 0, 0, comboItem1 );
|
|
table-><a href="ntqtable.html#setItem">setItem</a>( 1, 0, comboItem2 );
|
|
|
|
table-><a href="ntqtable.html#setItem">setItem</a>( 1, 1, checkItem1 );
|
|
table-><a href="ntqtable.html#setItem">setItem</a>( 0, 1, checkItem2 );
|
|
|
|
<a name="x2692"></a> table-><a href="ntqtable.html#setText">setText</a>( 1, 2, "Text" );
|
|
|
|
table-><a href="ntqtable.html#horizontalHeader">horizontalHeader</a>()->setLabel( 0, " Combos" );
|
|
table-><a href="ntqtable.html#horizontalHeader">horizontalHeader</a>()->setLabel( 1, "Checkboxes" );
|
|
table-><a href="ntqtable.html#verticalHeader">verticalHeader</a>()->setLabel( 0, "1" );
|
|
table-><a href="ntqtable.html#verticalHeader">verticalHeader</a>()->setLabel( 1, "2" );
|
|
|
|
// populate menubar
|
|
<a href="tqpopupmenu.html">TQPopupMenu</a>* fileMenu = new <a href="tqpopupmenu.html">TQPopupMenu</a>( this );
|
|
<a href="tqpopupmenu.html">TQPopupMenu</a>* helpMenu = new <a href="tqpopupmenu.html">TQPopupMenu</a>( this );
|
|
|
|
<a href="tqmainwindow.html#menuBar">menuBar</a>()->insertItem( "&File", fileMenu );
|
|
<a href="tqmainwindow.html#menuBar">menuBar</a>()->insertItem( "&Help", helpMenu );
|
|
|
|
int fileId = fileMenu-><a href="tqmenudata.html#insertItem">insertItem</a>( "E&xit", this, TQ_SLOT(<a href="tqwidget.html#close">close</a>()) );
|
|
|
|
int helpId = helpMenu-><a href="tqmenudata.html#insertItem">insertItem</a>( "Open Assistant", this, TQ_SLOT(assistantSlot()) );
|
|
|
|
// populate toolbar
|
|
<a href="tqtoolbar.html">TQToolBar</a>* toolbar = new <a href="tqtoolbar.html">TQToolBar</a>( this );
|
|
<a href="tqtoolbutton.html">TQToolButton</a>* assistantButton = new <a href="tqtoolbutton.html">TQToolButton</a>( toolbar );
|
|
<a name="x2694"></a> assistantButton-><a href="tqtoolbutton.html#setIconSet">setIconSet</a>( TQPixmap("appicon.png") );
|
|
</pre>
|
|
<p> A <a href="ntqtable.html">TQTable</a> is used as the central widget and the table, the menus
|
|
and the toolbar are populated.
|
|
<pre> <a name="x2699"></a> TQWhatsThis::<a href="ntqwhatsthis.html#whatsThisButton">whatsThisButton</a>( toolbar );
|
|
</pre>
|
|
<p> The static function whatsThisButton() creates a <a href="tqtoolbutton.html">TQToolButton</a>
|
|
which will enter "What's this?" mode when clicked.
|
|
<pre> //create tooltipgroup
|
|
<a href="tqtooltipgroup.html">TQToolTipGroup</a> * tipGroup = new <a href="tqtooltipgroup.html">TQToolTipGroup</a>( this );
|
|
<a name="x2697"></a> <a href="tqobject.html#connect">connect</a>( tipGroup, TQ_SIGNAL(<a href="tqtooltipgroup.html#showTip">showTip</a>(const <a href="tqstring.html">TQString</a>&)), statusBar(),
|
|
TQ_SLOT(message(const <a href="tqstring.html">TQString</a>&)) );
|
|
<a name="x2696"></a> <a href="tqobject.html#connect">connect</a>( tipGroup, TQ_SIGNAL(<a href="tqtooltipgroup.html#removeTip">removeTip</a>()), statusBar(), TQ_SLOT(clear()) );
|
|
</pre>
|
|
<p> A <a href="tqtooltipgroup.html">TQToolTipGroup</a> is created and will show and remove tooltips
|
|
in the statusbar as the tooltips are displayed on the widgets.
|
|
<pre> // set up tooltips
|
|
<a name="x2695"></a> TQToolTip::<a href="tqtooltip.html#add">add</a>( assistantButton, tr ("Open Assistant"), tipGroup, "Opens TQt Assistant" );
|
|
|
|
<a name="x2690"></a> horizontalTip = new HeaderToolTip( table-><a href="ntqtable.html#horizontalHeader">horizontalHeader</a>(), tipGroup );
|
|
<a name="x2693"></a> verticalTip = new HeaderToolTip( table-><a href="ntqtable.html#verticalHeader">verticalHeader</a>(), tipGroup );
|
|
|
|
cellTip = new TableToolTip( table, tipGroup );
|
|
</pre>
|
|
<p> The tooltips are set up. The static function add() sets up a
|
|
tooltip on the Assistant toolbutton. Tooltip objects are created
|
|
using the <a href="tqtooltip.html">TQToolTip</a> subclasses, the constructor's first parameter
|
|
specifies the widget we want to add dynamic tooltips for and the
|
|
second argument specifies the <a href="tqtooltipgroup.html">TQToolTipGroup</a> they should belong
|
|
to.
|
|
<pre> // set up whats this
|
|
<a name="x2698"></a> TQWhatsThis::<a href="ntqwhatsthis.html#add">add</a> ( assistantButton, "This is a toolbutton which opens Assistant" );
|
|
|
|
HeaderWhatsThis *horizontalWhatsThis = new HeaderWhatsThis( table-><a href="ntqtable.html#horizontalHeader">horizontalHeader</a>() );
|
|
HeaderWhatsThis *verticalWhatsThis = new HeaderWhatsThis( table-><a href="ntqtable.html#verticalHeader">verticalHeader</a>() );
|
|
|
|
TableWhatsThis *cellWhatsThis = new TableWhatsThis( table );
|
|
|
|
<a name="x2689"></a> fileMenu-><a href="tqmenudata.html#setWhatsThis">setWhatsThis</a>( fileId, "Click here to exit the application" );
|
|
helpMenu-><a href="tqmenudata.html#setWhatsThis">setWhatsThis</a>( helpId, "Click here to open Assistant" );
|
|
</pre>
|
|
<p> The WhatsThis help is set up. The static function add() adds
|
|
What's This? help for the toolbutton which opens Assistant.
|
|
Instances of the two WhatsThis subclasses are created for the
|
|
headers and the table. What's This? help is also added for the
|
|
menu items.
|
|
<pre> // connections
|
|
<a href="tqobject.html#connect">connect</a>( assistantButton, TQ_SIGNAL(<a href="ntqbutton.html#clicked">clicked</a>()), this, TQ_SLOT(assistantSlot()) );
|
|
<a href="tqobject.html#connect">connect</a>( horizontalWhatsThis, TQ_SIGNAL(linkClicked(const <a href="tqstring.html">TQString</a>&)), assistant,
|
|
TQ_SLOT(<a href="ntqassistantclient.html#showPage">showPage</a>(const <a href="tqstring.html">TQString</a>&)) );
|
|
<a href="tqobject.html#connect">connect</a>( verticalWhatsThis, TQ_SIGNAL(linkClicked(const <a href="tqstring.html">TQString</a>&)), assistant,
|
|
TQ_SLOT(<a href="ntqassistantclient.html#showPage">showPage</a>(const <a href="tqstring.html">TQString</a>&)) );
|
|
<a href="tqobject.html#connect">connect</a>( cellWhatsThis, TQ_SIGNAL(linkClicked(const <a href="tqstring.html">TQString</a>&)), assistant,
|
|
TQ_SLOT(<a href="ntqassistantclient.html#showPage">showPage</a>(const <a href="tqstring.html">TQString</a>&)) );
|
|
}
|
|
</pre>
|
|
<p> Signals and slots are connected, so that the relevant pages will
|
|
be displayed in TQt Assistant when clicking on a hyperlink or on
|
|
the assistant button.
|
|
<pre> MainWindow::~MainWindow()
|
|
{
|
|
delete horizontalTip;
|
|
delete verticalTip;
|
|
delete cellTip;
|
|
}
|
|
</pre>
|
|
<p> The destructor deletes the tooltips. We need to delete the
|
|
tooltips explicitly since <a href="tqtooltip.html">TQToolTip</a> is, as mentioned above, not
|
|
a subclass of <a href="tqobject.html">TQObject</a> and the instances of TQToolTip not will be
|
|
deleted when the widget is deleted.
|
|
<pre> void MainWindow::assistantSlot()
|
|
{
|
|
<a href="tqstring.html">TQString</a> docsPath = TQDir("../../doc").absPath();
|
|
<a name="x2686"></a> assistant-><a href="ntqassistantclient.html#showPage">showPage</a>( TQString("%1/html/ntqassistantclient.html").arg(docsPath) );
|
|
}
|
|
</pre>
|
|
<p> The assistantSlot() uses applicationDirPath() to find the
|
|
location of the documentation files and shows the specified page
|
|
in TQt Assistant.
|
|
|
|
|
|
<pre> #include <<a href="qapplication-h.html">ntqapplication.h</a>>
|
|
#include "mainwindow.h"
|
|
|
|
int main( int argc, char** argv )
|
|
{
|
|
<a href="ntqapplication.html">TQApplication</a> app( argc, argv );
|
|
MainWindow main;
|
|
main.<a href="tqwidget.html#show">show</a>();
|
|
<a name="x2701"></a> app.<a href="ntqapplication.html#setMainWidget">setMainWidget</a>( &main );
|
|
<a name="x2700"></a> return app.<a href="ntqapplication.html#exec">exec</a>();
|
|
}
|
|
</pre>
|
|
<p> The main function is a standard implementation opening
|
|
the application main window.
|
|
<p> To build the example go to the helpsystem directory
|
|
(TQTDIR/examples/helpsystem) run qmake to generate the makefile,
|
|
and use the make tool to build the library.
|
|
|
|
<hr>
|
|
<ol> <li><a name="footnote1"></a>
|
|
Note that <a href="moc.html#moc">moc</a> requires that <a href="tqobject.html">TQObject</a>
|
|
is the first base class. <a href="#footnote-call1">Back...</a> <li><a name="footnote2"></a>
|
|
|
|
Note that we have to explicitly scope the orientation
|
|
(TQObject or <a href="ntqwhatsthis.html">TQWhatsThis</a>) since HeaderWhatsThis uses multiple
|
|
inheritance. <a href="#footnote-call2">Back...</a></ol>
|
|
</hr><p>See also <a href="examples.html">Examples</a>.
|
|
|
|
<!-- eof -->
|
|
<p><address><hr><div align=center>
|
|
<table width=100% cellspacing=0 border=0><tr>
|
|
<td>Copyright © 2007
|
|
<a href="troll.html">Trolltech</a><td align=center><a href="trademarks.html">Trademarks</a>
|
|
<td align=right><div align=right>TQt 3.3.8</div>
|
|
</table></div></address></body>
|
|
</html>
|