1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
/****************************************************************************
**
** Copyright (C) 2009 Nokia Corporation and/or its subsidiary(-ies).
** Contact: Nokia Corporation (qt-info@nokia.com)
**
** This file is part of the documentation of the Qt Toolkit.
**
** $QT_BEGIN_LICENSE:LGPL$
** No Commercial Usage
** This file contains pre-release code and may not be distributed.
** You may use this file in accordance with the terms and conditions
** contained in the Technology Preview License Agreement accompanying
** this package.
**
** GNU Lesser General Public License Usage
** Alternatively, this file may be used under the terms of the GNU Lesser
** General Public License version 2.1 as published by the Free Software
** Foundation and appearing in the file LICENSE.LGPL included in the
** packaging of this file. Please review the following information to
** ensure the GNU Lesser General Public License version 2.1 requirements
** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
**
** In addition, as a special exception, Nokia gives you certain
** additional rights. These rights are described in the Nokia Qt LGPL
** Exception version 1.1, included in the file LGPL_EXCEPTION.txt in this
** package.
**
** If you have questions regarding the use of this file, please contact
** Nokia at qt-info@nokia.com.
**
**
**
**
**
**
**
**
** $QT_END_LICENSE$
**
****************************************************************************/
/*!
\page qt-embedded-envvars.html
\title Qt for Embedded Linux Environment Variables
\ingroup qt-embedded-linux
These environment variables are relevant to \l{Qt for Embedded Linux}
users.
\table
\header \o Variable \o Description
\row
\o \bold POINTERCAL_FILE \target POINTERCAL_FILE
\o Specifies the file containing the data used to calibrate the
pointer device.
See also QWSCalibratedMouseHandler and \l{Qt for Embedded Linux Pointer
Handling}.
\row
\o \bold QT_ONSCREEN_PAINT \target QT_ONSCREEN_PAINT
\o If defined, the application will render its widgets directly on
screen. The affected regions of the screen will not be modified by
the screen driver unless another window with a higher focus
requests (parts of) the same region.
Setting this environment variable is equivalent to setting the
Qt::WA_PaintOnScreen attribute for all the widgets in the
application.
See also the Qt for Embedded Linux \l{Qt for Embedded Linux Architecture#Graphics
Rendering}{graphics rendering} documentation.
\row
\o \bold QWS_SW_CURSOR \target QWS_SW_CURSOR
\o If defined, the software mouse cursor is always used (even when using an
accelerated driver that supports a hardware cursor).
\row
\o \bold QWS_DISPLAY \target QWS_DISPLAY
\o
Specifies the display type and framebuffer. For example, if the
current shell is bash, ksh, zsh or sh:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 0
The valid values for the \c <driver> argument are \c LinuxFb, \c
QVFb, \c VNC, \c Transformed, \c Multi and \l
{QScreenDriverPlugin::keys()}{keys} identifying custom drivers,
and the \c {<display num>} argument is used to separate screens
that are using the same screen driver and to enable multiple
displays (see the \l {Running Qt for Embedded Linux Applications}
documentation for more details).
The driver specific options are described in the \l{Qt for Embedded Linux
Display Management}{display management} documentation.
\row
\o \bold QWS_SIZE \target QWS_SIZE
\o
Specifies the size of the \l{Qt for Embedded Linux} window which is centered
within the screen. For example, if the current shell is bash, ksh,
zsh or sh:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 1
\row
\o \bold QWS_MOUSE_PROTO \target QWS_MOUSE_PROTO
\o
Specifies the driver for pointer handling. For example, if the
current shell is bash, ksh, zsh or sh:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 2
The valid values for the \c <driver> argument are \c MouseMan, \c
IntelliMouse, \c Microsoft, \c VR41xx, \c LinuxTP, \c Yopy. \c
Tslib and \l {QMouseDriverPlugin::keys()}{keys} identifying
custom drivers, and the driver specific options are typically a
device, e.g., \c /dev/mouse for mouse devices and \c /dev/ts for
touch panels.
Multiple keyboard drivers can be specified in one go:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 3
Input will be read from all specified drivers.
Note that the \c Vr41xx driver also accepts two optional
arguments: \c press=<value> defining a mouseclick (the default
value is 750) and \c filter=<value> specifying the length of the
filter used to eliminate noise (the default length is 3). For
example:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 4
See also \l {Qt for Embedded Linux Pointer Handling}.
\row
\o \bold QWS_KEYBOARD \target QWS_KEYBOARD
\o
Specifies the driver and device for character input. For example, if the
current shell is bash, ksh, zsh or sh:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 5
The valid values for the \c <driver> argument are \c SL5000, \c
Yopy, \c VR41xx, \c TTY, \c USB and \l
{QKbdDriverPlugin::keys()}{keys} identifying custom drivers,
and the driver specific options are typically a device, e.g., \c
/dev/tty0.
Multiple keyboard drivers can be specified in one go:
\snippet doc/src/snippets/code/doc_src_emb-envvars.qdoc 6
Input will be read from all specified drivers.
See also \l {Qt for Embedded Linux Character Input}.
\endtable
*/
|
