| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
Instead of having separate handlers for each property, just handle all of them
in one handler for emuMB, and one handler for emuWheel.
|
|
|
|
| |
Numbers are so lame, defines are all the rage now I've heard.
|
|
|
|
| |
Don't enable wheel emulation with 0 inertia - bad things happen.
|
|
|
|
| |
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
| |
Keycodes over 255 are silently ignored in the server. The least we can do is
put a warning in the logs.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
|
| |
Remove code duplication, let the mapping function hand us the actual button
event to be passed up to the server.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
|
|
| |
Fixes file descriptor leak.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
With this fix, on my PowerBook HAL hotplugging correctly detects my USB mouse,
and no longer thinks keyboards have random numbers of mouse buttons. :)
The LONG_BITS and NBITS macro definitions are stolen from xf86-input-synaptics.
Signed-off-by: Michel Dänzer <michel@tungstengraphics.com>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
| |
|
| |
|
|
|
|
|
| |
Report correct versions instead of
"compiled for 0.0.0, module version = 1.0.0"
|
|
|
|
|
|
|
| |
After suspend/resume, sometimes the device doesn't come back up on the same
node. Since we do not call PreInit for the device (which would detect this
situation), we continue to try to read a nonexisting file, spamming the log
file with "Read Error".
|
| |
|
| |
|
|
|
|
| |
We're not building with or without XInput. Same with xkb.
|
|
|
|
| |
Hook taken from xserver's Makefile.am
|
|
|
|
|
| |
Fix up licence of emuMB.c, was using Red Hat instead of "The authors", but
this code wasn't contributed by RH anyway.
|
|
|
|
|
| |
Ctrl+Alt+Backspace works, I'm using it daily.
CapsLock doesn't repeat, otherwise we wouldn't have Bug 16318.
|
|
|
|
| |
Conversion is now done in the DIX.
|
|
|
|
|
|
| |
greater than BTN_TASK.
Signed-off-by: Peter Hutterer <peter@cs.unisa.edu.au>
|
|
|
|
|
|
| |
We don't really do anything with the number other than print it since I'm sure
that half the mice don't report the correct number anyway (especially with the
wheel button mapping). But having a bit more debug info is good.
|
| |
|
|
|
|
| |
Follow-up to 76800bfa75807e49398380b902f6c0f547cd4c0e.
|
|
|
|
| |
Signed-off-by: Peter Hutterer <peter@cs.unisa.edu.au>
|
|
|
|
|
|
|
|
| |
This ensures that the middle button emulation is re-enabled after VT switch,
otherwise the block handler that deals with the timeouts would not get
re-registered.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
| |
|
|
|
|
|
| |
This avoids segfaults when HAL is restarted behind our backs. Also, only init
MB emulation when the device actually has a button.
|
|
|
|
| |
1.99.3 had a nasty bug, so here's a quick update.
|
|
|
|
|
|
| |
Default setting is still "on" until middle button is pressed. If the options
is however explicitly stated in the config file, it takes the value from the
config file, no matter if a middle button is present.
|
|
|
|
| |
Less SIGABRTs are less exciting, but sometimes boredom is what we want.
|
| |
|
|
|
|
|
|
| |
Devices may report middle mouse buttons even if they don't have one (PS/2
devices just don't know any better), so we can't be sure until we see the
event.
|
|
|
|
| |
Ported from xf86-input-mouse, with a few cleanups.
|
| |
|
|
|
|
|
|
|
|
|
| |
The commit b4a5a204 fixed an issue, where we can't move the pointer to
other screens and this happens in current master branch again. This commit
ports the old commit to the current master branch.
Signed-off-by: Sven Wegener <swegener@gentoo.org>
Signed-off-by: Peter Hutterer <peter@cs.unisa.edu.au>
|
|
|
|
| |
Thanks to Sven Wegener for pointing out the incorrect previous version.
|
|
|
|
|
|
|
| |
GetMotionEvents() doesn't exist, led to compile errors with servers pre-MPX
merge. Thanks to Sven Wegener for pointing this out.
This reverts commit 42422d8f69e6806e1adfd93017cac064a75041c7.
|
| |
|
|
|
|
|
|
|
|
|
| |
If the grab fails, this is most likely a sign that the device has been grabbed
already (probably by a device specified in xorg.conf). So let's not add the
device to the server's input device list, since it won't generate events
anyway.
Exception: keyboards and kernel 2.4 are not affected.
|
| |
|
|
|
|
| |
Signed-off-by: Peter Hutterer <peter@cs.unisa.edu.au>
|
| |
|
|
|
|
|
|
|
| |
In the mouse driver, these options are only used if XFree86LOADER is
undefined. configure.ac in the xserver forces said define to 1 if we're
building the xfree86 DDX, so I don't see the point of having them around.
Especially since they weren't used in evdev anyway.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a bit of a mess. The MS Optical Desktop 2000 registers both relative
and absolute axes on the same device (the mouse). The absolute axes have a
valid min/max range for x/y and thus overwrite the x/y relative axes in the
server (no, this is not a server bug). And I wouldn't be surprised if other
devices have similar issues.
Since the device only sends relative events after that, the mouse is
essentially restricted to the min..max range of 0..255. The server simply
doesn't do unrestricted relative axis and restricted absolute axis on the same
device (not for the same axis numbers anyway).
|
|
|
|
| |
Stopps meta/super key from autorepeating
|
|
|
|
| |
Pretty much dead code anyway.
|
|
|
|
|
| |
Some Microsoft mice have this wrong. And it seems like a sensible thing
to do anyway.
|