~oif-team/ubuntu/natty/qt4-x11/xi2.1

<td width="1">  </td><td class="postheader" 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>

[Previous: <a href="designer-resources.html">Editing Resources with Qt Designer</a>]

[<a href="designer-manual.html">Contents</a>]

[Next: <a href="designer-using-a-component.html">Using a Component in Your Application</a>]

</p>

<h1 align="center">Using Custom Widgets with Qt Designer</h1>

<p><i>Qt Designer</i> can display custom widgets through its extensible plugin mechanism, allowing the range of designable widgets to be extended by the user and third parties. This feature also allows <i>Qt Designer</i> to optionally support <a href="qt3support.html">Qt 3 compatibility widgets</a>. Alternatively, it is possible to use existing widgets as placeholders for widget classes that provide similar APIs.</p>

<ul><li><a href="#handling-custom-widgets">Handling Custom Widgets</a></li>

<ul><li><a href="#promoting-widgets">Promoting Widgets</a></li>

<li><a href="#user-defined-custom-widgets">User Defined Custom Widgets</a></li>

</ul>

<p>Widgets from the <a href="qt3support.html#qt3support">Qt3Support</a> library are made available via in <i>Qt Designer</i>'s support for custom widgets.</p>

<h2>Handling Custom Widgets</h2>

<p>Although <i>Qt Designer</i> supports all of the standard Qt widgets, and can be configured to handle widgets supplied in the <a href="qt3support.html#qt3support">Qt3Support</a> library, some specialized widgets may not be available as standard for a number of reasons:</p>

<ul>

<li>Custom widgets may not be available at the time the user interface is being designed.</li>

<li>Custom widgets may be platform-specific, and designers may be developing the user interface on a different platform to end users.</li>

<li>The source code for a custom widget is not available, or the user interface designers are unable to use the widget for non-technical reasons.</li>

</ul>

<p>In the above situations, it is still possible to design forms with the aim of using custom widgets in the application. To achieve this, we can use the widget promotion feature of <i>Qt Designer</i>.</p>

<p>In all other cases, where the source code to the custom widgets is available, we can adapt the custom widget for use with <i>Qt Designer</i>.</p>

<h3>Promoting Widgets</h3>

<center><img src="images/designer-promoting-widgets.png" /></center><p>In the case where forms must be designed, but where certain custom widgets are unavailable to the designer, we can substitute similar widgets to represent the missing widgets. For example, we might represent instances of a custom push button class, <tt>MyPushButton</tt>, with instances of <a href="qpushbutton.html">QPushButton</a> and promote these to <tt>MyPushButton</tt> so that <a href="uic.html">uic</a> generates suitable code for this missing class.</p>

<p>When choosing a widget to use as a placeholder, it is useful to compare the API of the missing widget with those of standard Qt widgets. For specialized widgets that subclass standard classes, the obvious choice of placeholder is the base class of the custom widget; for example, <a href="qslider.html">QSlider</a> might be used for specialized <a href="qslider.html">QSlider</a> subclasses.</p>

<p>For specialized widgets that do not share a common API with standard Qt widgets, it is worth considering adapting a custom widget for use in <i>Qt Designer</i>. If this is not possible then <a href="qwidget.html">QWidget</a> is the obvious choice for a placeholder widget since it is the lowest common denominator for all widgets.</p>

<h3>User Defined Custom Widgets</h3>

<center><img src="images/customwidgetplugin-example.png" /></center><p>Custom widgets can be adapted for use with <i>Qt Designer</i>, giving designers the opportunity to configure the user interface using the actual widgets that will be used in an application rather than placeholder widgets.</p>

<p>The process of creating a custom widget plugin is described in the <a href="designer-customwidgetplugin.html">Custom Widget Plugin</a> example. To use a plugin, it is necessary to ensure that it is located on a path that <i>Qt Designer</i> searches for plugins. Generally, plugins stored in <tt>$QTDIR/plugins/designer</tt> will be loaded when <i>Qt Designer</i> starts.</p>

<p>

[Previous: <a href="designer-resources.html">Editing Resources with Qt Designer</a>]

[<a href="designer-manual.html">Contents</a>]

[Next: <a href="designer-using-a-component.html">Using a Component in Your Application</a>]

</p>

<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>

</tr></table></div></address></body>

</html>

Older »