|
|
|
|
<!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/doc/winsystem.doc:36 -->
|
|
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
|
|
|
|
<title>Window System-specific Notes</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>Window System-specific Notes</h1>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<p> TQt is a multiplatform GUI toolkit, so almost the entire API is the
|
|
|
|
|
same on all platforms and window systems. If you wish to use
|
|
|
|
|
platform-specific features, and still maintain a platform-independent
|
|
|
|
|
source tree, you should protect the platform-specific code using the
|
|
|
|
|
appropriate <tt>#ifdef</tt> statements (see below).
|
|
|
|
|
<p> <!-- toc -->
|
|
|
|
|
<ul>
|
|
|
|
|
<li><a href="#1"> TQt/X11
|
|
|
|
|
</a>
|
|
|
|
|
<li><a href="#2"> TQt/Windows
|
|
|
|
|
</a>
|
|
|
|
|
<ul>
|
|
|
|
|
<li><a href="#2-1"> Microsoft Visual Studio 2005 Deployment Issues
|
|
|
|
|
</a>
|
|
|
|
|
</ul>
|
|
|
|
|
<li><a href="#3"> TQt/Mac OS X
|
|
|
|
|
</a>
|
|
|
|
|
<li><a href="#4"> TQt/Embedded
|
|
|
|
|
</a>
|
|
|
|
|
</ul>
|
|
|
|
|
<!-- endtoc -->
|
|
|
|
|
|
|
|
|
|
<p> For information about which platforms are supported by TQt, see the
|
|
|
|
|
<a href="http://www.trolltech.com/products/platforms/">Platform
|
|
|
|
|
Notes</a>. For information on distributing TQt applications, see
|
|
|
|
|
<a href="distributingqt.html">Deploying TQt Applications</a>.
|
|
|
|
|
<p> <a name="x11"></a>
|
|
|
|
|
<h2> TQt/X11
|
|
|
|
|
</h2>
|
|
|
|
|
<a name="1"></a><p> When compiling for this platform, the macro <tt>Q_WS_X11</tt> is defined.
|
|
|
|
|
<p> <em>Not documented here. Please contact Trolltech Technical Support if you have queries.</em>
|
|
|
|
|
<p> <center><img src="dependencies.png" alt="TQt/X11 Dependencies"></center>
|
|
|
|
|
<p> Note: You must compile with <em>both</em> Xft and XRender support to get
|
|
|
|
|
alpha transparency support for pixmaps and images. Configuring with
|
|
|
|
|
XRender support only is not enough.
|
|
|
|
|
<p> <a name="win"></a>
|
|
|
|
|
<h2> TQt/Windows
|
|
|
|
|
</h2>
|
|
|
|
|
<a name="2"></a><p> When compiling for this platform, the macro <tt>Q_WS_WIN</tt> is defined.
|
|
|
|
|
<p> <em>Not documented here. Please contact Trolltech Technical Support if you have queries.</em>
|
|
|
|
|
<p> <h3> Microsoft Visual Studio 2005 Deployment Issues
|
|
|
|
|
</h3>
|
|
|
|
|
<a name="2-1"></a><p> Executables compiled with Microsoft Visual Studio 2005 require
|
|
|
|
|
a manifest file that points to the C and C++ runtime libraries that
|
|
|
|
|
TQt and the application itself depend on. The manifest file is
|
|
|
|
|
automatically generated for you, but it always needs to be located
|
|
|
|
|
in the same directory as the application executable.
|
|
|
|
|
<p> It is important to remember to deploy the manifest file when
|
|
|
|
|
deploying an application.
|
|
|
|
|
<p> <b>Note:</b>
|
|
|
|
|
If you don't want to deploy your application with the .manifest file,
|
|
|
|
|
you can embed the manifest in the executable as a resource with the
|
|
|
|
|
<tt>mt</tt> command (distributed with Visual Studio 2005).
|
|
|
|
|
<p> If you have further problems, please see the MSDN document,
|
|
|
|
|
"Side-by-side Assemblies Reference".
|
|
|
|
|
<p> <a name="macosx"></a>
|
|
|
|
|
<h2> TQt/Mac OS X
|
|
|
|
|
</h2>
|
|
|
|
|
<a name="3"></a><p> When compiling for this platform, the macro <tt>Q_WS_MACX</tt> is defined.
|
|
|
|
|
<p> <ul>
|
|
|
|
|
<li> <a href="mac-differences.html">TQt/Mac issues</a>
|
|
|
|
|
</ul>
|
|
|
|
|
<p> <a name="qws"></a>
|
|
|
|
|
<h2> TQt/Embedded
|
|
|
|
|
</h2>
|
|
|
|
|
<a name="4"></a><p> When compiling for this platform, the macro <tt>Q_WS_QWS</tt> is defined
|
|
|
|
|
(the window system is literally the TQt Window System).
|
|
|
|
|
<p> <ul>
|
|
|
|
|
<li> <a href="emb-install.html">Installation</a>
|
|
|
|
|
<li> <a href="emb-performance.html">TQt/Embedded performance tuning</a>
|
|
|
|
|
<li> <a href="emb-running.html">Running TQt/Embedded applications</a>
|
|
|
|
|
<li> <a href="emb-porting.html">Porting your applications to TQt/Embedded</a>
|
|
|
|
|
<li> <a href="emb-fonts.html">Font formats and definitions</a>
|
|
|
|
|
<li> <a href="emb-charinput.html">Character input (keyboard, pen, ...)</a>
|
|
|
|
|
<li> <a href="emb-pointer.html">Pointer handling (mouse, pen, ...)</a>
|
|
|
|
|
<li> <a href="emb-features.html">Reduce memory use with the feature definition file</a>
|
|
|
|
|
</ul>
|
|
|
|
|
<p>
|
|
|
|
|
<!-- 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>
|
