XSetDeviceMode(3X11) X FUNCTIONS XSetDeviceMode(3X11)NAME
XSetDeviceMode - change the mode of a device
SYNTAX
XSetDeviceMode(display, device, mode)
Display *display;
XDevice *device;
int _mode;
ARGUMENTS
display Specifies the connection to the X server.
device Specifies the device whose mode is to be changed.
mode Specifies the mode. You can pass Absolute , or Relative.
DESCRIPTION
The XSetDeviceMode request changes the mode of an input device that is capable of reporting either absolute positional information or rela-
tive motion information. Not all input devices are capable of reporting motion data, and not all are capable of changing modes from Abso-
lute to Relative.
XSetDeviceMode can generate a BadDevice or BadMode error.
DIAGNOSTICS
BadDevice An invalid device was specified. The specified device does not exist or has not been opened by this client via XOpenInputDe-
vice. This error may also occur if some other client has caused the specified device to become the X keyboard or X pointer
device via the XChangeKeyboardDevice or XChangePointerDevice requests.
BadMatch This error may occur if an XSetDeviceMode request is made specifying a device that has no valuators and reports no axes of
motion.
BadMode An invalid mode was specified. This error will also be returned if the specified device is not capable of supporting the XSet-
DeviceMode request.
SEE ALSO
Programming with Xlib
XFree86 Version 4.7.0 XSetDeviceMode(3X11)
Check Out this Related Man Page
XSetDeviceMode(3) X FUNCTIONS XSetDeviceMode(3)NAME
XSetDeviceMode - change the mode of a device
SYNTAX
XSetDeviceMode(display, device, mode)
Display *display;
XDevice *device;
int _mode;
ARGUMENTS
display Specifies the connection to the X server.
device Specifies the device whose mode is to be changed.
mode Specifies the mode. You can pass Absolute , or Relative.
DESCRIPTION
The XSetDeviceMode request changes the mode of an input device that is capable of reporting either absolute positional information or rela-
tive motion information. Not all input devices are capable of reporting motion data, and not all are capable of changing modes from Abso-
lute to Relative.
XSetDeviceMode can generate a BadDevice or BadMode error.
DIAGNOSTICS
BadDevice An invalid device was specified. The specified device does not exist or has not been opened by this client via XOpenInputDe-
vice. This error may also occur if some other client has caused the specified device to become the X keyboard or X pointer
device via the XChangeKeyboardDevice or XChangePointerDevice requests.
BadMatch This error may occur if an XSetDeviceMode request is made specifying a device that has no valuators and reports no axes of
motion.
BadMode An invalid mode was specified. This error will also be returned if the specified device is not capable of supporting the XSet-
DeviceMode request.
SEE ALSO
Programming with Xlib
X Version 11 libXi 1.2.1 XSetDeviceMode(3)
There is no xorg.conf file and no XF86Config file on a certain FreeBSD machine:
# locate xorg.conf
/usr/local/man/man5/xorg.conf.5.gz
# locate XF86Config
#
Can someone let me know if that means that there is a bare bones set up possible only? xrandr works fine, but I am looking for ways to... (6 Replies)
I'm looking for finer granularity than the 20 ANSI escape sequence screen modes. What I'd like to do is have the terminal increase it's own height when I have to show the user a long menu.
Platform is Cygwin 64 running over Win 7 Pro.
Mike (4 Replies)
What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file.
# When the shell exits, append to the history file instead of overwriting it
shopt -s histappend (3 Replies)
Look this very good rendering on Slackware 14.2
in my opinion is near perfect.
https://i.stack.imgur.com/q5trL.png
Now look the same page on Fedora 30
https://i.stack.imgur.com/FBQv7.png
In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)