{"id":327,"date":"2014-11-10T19:47:06","date_gmt":"2014-11-10T11:47:06","guid":{"rendered":"http:\/\/www.datarelab.com\/blog\/?p=327"},"modified":"2015-01-18T19:03:12","modified_gmt":"2015-01-18T11:03:12","slug":"qt-for-embedded-linux-environment-variables","status":"publish","type":"post","link":"https:\/\/www.datarelab.com\/blog\/Technical_literature\/327.html","title":{"rendered":"Qt for Embedded Linux Environment Variables"},"content":{"rendered":"

These environment variables are relevant to Qt for Embedded Linux<\/a> users.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Variable<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
POINTERCAL_FILE<\/b><\/a><\/td>\nSpecifies the file containing the data used to calibrate the pointer device.See also QWSCalibratedMouseHandler<\/a> and Qt for Embedded Linux Pointer Handling<\/a>.<\/td>\n<\/tr>\n
QT_ONSCREEN_PAINT<\/b><\/a><\/td>\nIf 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<\/a> attribute for all the widgets in the application.See also the Qt for Embedded Linux graphics rendering<\/a> documentation.<\/td>\n<\/tr>\n
QWS_SW_CURSOR<\/b><\/a><\/td>\nIf defined, the software mouse cursor is always used (even when using an accelerated driver that supports a hardware cursor).<\/td>\n<\/tr>\n
QWS_DISPLAY<\/b><\/a><\/td>\nSpecifies the display type and framebuffer. For example, if the current shell is bash, ksh, zsh or sh:<\/p>\n
 export QWS_DISPLAY=<driver>[:<driver specific options>]...\r\n         [:<display num>]<\/pre>\n
The valid values for the <driver><\/tt> argument are LinuxFb<\/tt>, QVFb<\/tt>, VNC<\/tt>, Transformed<\/tt>, Multi<\/tt> and keys<\/a> identifying custom drivers, and the <display num><\/tt> argument is used to separate screens that are using the same screen driver and to enable multiple displays (see the Running Qt for Embedded Linux Applications<\/a> documentation for more details).<\/p>\n
The driver specific options are described in the display management<\/a> documentation.<\/td>\n<\/tr>\n
QWS_SIZE<\/b><\/a><\/td>\nSpecifies the size of the Qt for Embedded Linux<\/a> window which is centered within the screen. For example, if the current shell is bash, ksh, zsh or sh:<\/p>\n
 export QWS_SIZE=<width>x<height><\/pre>\n<\/td>\n<\/tr>\n
QWS_MOUSE_PROTO<\/b><\/a><\/td>\nSpecifies the driver for pointer handling. For example, if the current shell is bash, ksh, zsh or sh:<\/p>\n
 export QWS_MOUSE_PROTO=<driver>[:<driver specific options>]<\/pre>\n
The valid values for the <driver><\/tt> argument are MouseMan<\/tt>, IntelliMouse<\/tt>, Microsoft<\/tt>, VR41xx<\/tt>, LinuxTP<\/tt>, Yopy<\/tt>. Tslib<\/tt> and keys<\/a> identifying custom drivers, and the driver specific options are typically a device, e.g., \/dev\/mouse<\/tt> for mouse devices and\/dev\/ts<\/tt> for touch panels.<\/p>\n
Multiple keyboard drivers can be specified in one go:<\/p>\n
 export QWS_MOUSE_PROTO=\"<driver>[:<driver specific options>]\r\n         <driver>[:<driver specific options>]\r\n         <driver>[:<driver specific options>]\"<\/pre>\n
Input will be read from all specified drivers. Note that the Vr41xx<\/tt> driver also accepts two optional arguments: press=<value><\/tt> defining a mouseclick (the default value is 750) and filter=<value><\/tt> specifying the length of the filter used to eliminate noise (the default length is 3). For example:<\/p>\n
 export QWS_MOUSE_PROTO=\"Vr41xx:press=500:\/dev\/misc\/ts\"<\/pre>\n
See also Qt for Embedded Linux Pointer Handling<\/a>.<\/td>\n<\/tr>\n
QWS_KEYBOARD<\/b><\/a><\/td>\nSpecifies the driver and device for character input. For example, if the current shell is bash, ksh, zsh or sh:<\/p>\n
 export QWS_KEYBOARD=<driver>[:<driver specific options>]<\/pre>\n
The valid values for the <driver><\/tt> argument are SL5000<\/tt>, Yopy<\/tt>, VR41xx<\/tt>, TTY<\/tt>, USB<\/tt> and keys<\/a> identifying custom drivers, and the driver specific options are typically a device, e.g., \/dev\/tty0<\/tt>.<\/p>\n
Multiple keyboard drivers can be specified in one go:<\/p>\n
 export QWS_KEYBOARD=\"<driver>[:<driver specific options>]\r\n         <driver>[:<driver specific options>]\r\n         <driver>[:<driver specific options>]\"<\/pre>\n
Input will be read from all specified drivers.<\/p>\n
See also Qt for Embedded Linux Character Input<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"
These environment variables are relevant to Qt for Embe […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[152],"class_list":["post-327","post","type-post","status-publish","format-standard","hentry","category-Technical_literature","tag-qt"],"views":1514,"_links":{"self":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/posts\/327","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/comments?post=327"}],"version-history":[{"count":0,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/posts\/327\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/media?parent=327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/categories?post=327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.datarelab.com\/blog\/wp-json\/wp\/v2\/tags?post=327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}