<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- /home/gvatteka/dev/qt-4.3/doc/src/emb-pointer.qdoc -->
<head>
<title>Qtopia Core Pointer Handling</title>
<link href="classic.css" rel="stylesheet" type="text/css" />
</head>
<body>
<h1 align="center">Qtopia Core Pointer Handling<br /><small></small></h1>
<p>When running a Qtopia Core</tt> application, it either runs as a server or connects to an existing server. The mouse driver is loaded by the server application when it starts running, using Qt's <a href="plugins-howto.html">plugin system</tt></a>.</p>
<p>Internally in the client/server protocol, all system generated events, including pointer events, are passed to the server application which then propagates the event to the appropiate client. Note that pointer handling in Qtopia Core</tt> works for both mouse and mouse-like devices such as touch panels and trackballs.</p>
<p>Contents:</p>
<ul><li><a href="#available-drivers">Available Drivers</a></li>
<li><a href="#specifying-a-driver">Specifying a Driver</a></li>
<li><a href="#troubleshooting">Troubleshooting</a></li>
<ul><li><a href="#device-files">Device Files</a></li>
<li><a href="#file-permissions">File Permissions</a></li>
</ul>
</ul>
<a name="available-drivers"></a>
<h2>Available Drivers</h2>
<p>Qtopia Core</tt> provides ready-made drivers for the MouseMan, IntelliMouse, Microsoft, NEC Vr41XX, Linux Touch Panel and Yopy protocols as well as the universal touch screen library, tslib. Run the <tt>configure</tt> script to list the available drivers:</p>
<pre> ./configure -help</pre>
<p>In the default Qt configuration, only the "pc" mouse driver is enabled. The various drivers can be enabled and disabled using the <tt>configure</tt> script. For example:</p>
<pre> configure -qt-mouse-tslib</pre>
<p>Custom mouse drivers can be implemented by subclassing the QWSMouseHandler class and creating a mouse driver plugin (derived from the QMouseDriverPlugin class). Qtopia Core</tt>'s implementation of the QMouseDriverFactory class will automatically detect the plugin, loading the driver into the server application at runtime.</p>
<p>If you are creating a driver for a device that needs calibration or noise reduction, such as a touchscreen, derive from the QWSCalibratedMouseHandler subclass instead to take advantage of its calibration functionality.</p>
<a name="specifying-a-driver"></a>
<h2>Specifying a Driver</h2>
<p>Provided that the "pc" mouse driver is enabled, Qtopia Core</tt> will try to auto-detect the mouse device if it is one of the supported types on <tt>/dev/psaux</tt> or one of the <tt>/dev/ttyS</tt>? serial lines. If multiple mice are detected, all may be used simultaneously.</p>
<p>Note that Qtopia Core</tt> does not support auto-detection of <i>touch panels</i> in which case the driver must be specified explicitly to determine which device to use.</p>
<p>To manually specify which driver to use, set the <a href="qtopiacore-envvars.html#qws-mouse-proto"><tt>QWS_MOUSE_PROTO</tt></a> environment variable. For example (if the current shell is bash, ksh, zsh or sh):</p>
<pre> export QWS_MOUSE_PROTO=<driver>[:<driver specific options>]</pre>
<p>The valid values for the <tt><driver></tt> argument are <tt>MouseMan</tt>, <tt>IntelliMouse</tt>, <tt>Microsoft</tt>, <tt>VR41xx</tt>, <tt>LinuxTP</tt>, <tt>Yopy</tt>, <tt>Tslib</tt> and keys</tt> identifying custom drivers, and the driver specific options are typically a device, e.g., <tt>/dev/mouse</tt> for mouse devices and <tt>/dev/ts</tt> for touch panels.</p>
<p>Multiple mouse drivers can be specified in one go:</p>
<pre> export QWS_MOUSE_PROTO="<driver>[:<driver specific options>]
<driver>[:<driver specific options>]
<driver>[:<driver specific options>]"</pre>
<p>Input will be read from all specified drivers.</p>
<p>Note that the <tt>Vr41xx</tt> driver also accepts two optional arguments: <tt>press=<value></tt> defining a mouse click (the default value is 750) and <tt>filter=<value></tt> specifying the length of the filter used to eliminate noise (the default length is 3). For example:</p>
<pre> export QWS_MOUSE_PROTO="Vr41xx:press=500:/dev/misc/ts"</pre>
<p><table align="center" cellpadding="2" cellspacing="1" border="0">
<thead><tr valign="top" class="qt-style"><th>The Tslib Mouse Driver</th></tr></thead>
<tr valign="top" class="odd"><td>The tslib mouse driver inherits the QWSCalibratedMouseHandler class, providing calibration and noise reduction functionality in addition to generating mouse events for devices using the Universal Touch Screen Library.<p>To be able to compile this mouse handler, Qtopia Core</tt> must be configured with the <tt>-qt-mouse-tslib</tt> option as described above. In addition, the tslib headers and library must be present in the build environment.</p>
<p>The tslib sources can be downloaded from <a href="http://tslib.berlios.de">http://tslib.berlios.de</tt></a>. Use the <tt>configure</tt> script's -L and -I options to explicitly specify the location of the library and its headers:</p>
<pre> ./configure -L <path to tslib library> -I <path to tslib headers></pre>
<p>In order to use this mouse driver, tslib must also be correctly installed on the target machine. This includes providing a <tt>ts.conf</tt> configuration file and setting the neccessary environment variables (see the README file provided with tslib for details).</p>
<p>The <tt>ts.conf</tt> file will usually contain the following two lines:</p>
<pre> module_raw input
module linear</pre>
<p>To make Qtopia Core</tt> explicitly choose the tslib mouse handler, set the <a href="qtopiacore-envvars.html#qws-mouse-proto"><tt>QWS_MOUSE_PROTO</tt></a> environment variable as explained above.</p>
</td></tr>
</table></p>
<a name="troubleshooting"></a>
<h2>Troubleshooting</h2>
<a name="device-files"></a>
<h3>Device Files</h3>
<p>Make sure you are using the correct device file.</p>
<p>As a first step, you can test whether the device file actually gives any output. For instance, if you have specified the mouse driver with</p>
<pre> QWS_MOUSE_PROTO=IntelliMouse:/dev/input/mouse0}</pre>
<p>then try examining the output from the device by entering the following command in a console:</p>
<pre> cat /dev/input/mouse0 | hexdump</pre>
<p>If you see output from the device printed on the console when you move the mouse, you are probably using the correct device file; otherwise, you will need to experiment to find the correct device file.</p>
<a name="file-permissions"></a>
<h3>File Permissions</h3>
<p>Make sure you have sufficient permissions to access the device file.</p>
<p>The Qtopia Core server process needs at least read permission for the device file. Some drivers also require write access to the device file. For instance, if you have specified the mouse driver with</p>
<pre> QWS_MOUSE_PROTO=IntelliMouse:/dev/input/mouse0</pre>
<p>then examine the permissions of the device file by entering the following command in a console:</p>
<pre> chmod a+rw /dev/input/mouse0</pre>
<p>If the device file is actually a symbolic link to another file, you must change the permissions of the actual file instead.</p>
<p /><address><hr /><div align="center">
<table width="100%" cellspacing="0" border="0"><tr class="address">
<td width="30%">Copyright © 2007 <a href="trolltech.html">Trolltech</a></td>
<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>
<td width="30%" align="right"><div align="right">Qt Jambi </div></td>
</tr></table></div></address></body>
</html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
a6711891ce757817bba854bf3f25205a
>
files
>
2420
