| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This avoids segfaults when HAL is restarted behind our backs. Also, only init
MB emulation when the device actually has a button.
|
|
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.
|
|
Not many mice do this, but some do, Apple Mighty Mouse in particular, and
it makes click-and-drag pretty much impossible to use.
Arguably we should filter _all_ repeat events from the kernel and handle
synthesizing them in the server.
|
|
Don't do this in the button map. That's writeable by clients, which means
they have the chance to get it wrong. Just swap right and middle around
in event dispatch before you get to the user's map.
|
|
Or at least, refuse to recognise the config option. It's nonsensical to
use a model of something other than evdev, and it'll just break if you try.
|
|
Fixes 2b334d6b69d7dde5d553c638e134ebdf974749f3.
|
|
|
|
|
|
|
|
Even though we don't have keycodes for anything above 127, make sure our
map always covers up to 255. This ensures that the keycode range never
changes.
Spiritually cherry-picked from a9e87f29ccdadebb0742317bb57d66eaaca4b593
and 6db4a9fb84f828f745202c3fddc58d389fca220b.
|
|
There are two major classes here, touchscreens and touchpads. Touchpads
are logically more like relative devices, in that your initial touch
should not warp the cursor. So attempt to detect touchpads (via the
existence of BTN_TOUCH) and translate absolute events from those devices
to relative motion.
|
|
It did nothing, and the core won't invoke it anymore anyway.
|
|
Almost entirely taken from a patch I did ages ago in bug #3912, with
slight cleanups, and with the KcCGST options removed as per evdev 1.x.
|
|
The hotplug core passes Path not Device. With this change, hotplugging
works.
|
|
|
|
Spiritually cherry-picked from 036b457c1b3f7d2d174da890cb8598d907181f8e
|
|
Build evdevModuleData, et al, unconditionally.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
installed. Allow the use of evdev for mice on 2.4 kernels.
|
|
|
|
issues when input goes to multiple places. Restrict building the evdev
driver to 2.6 kernels since EVIOCGRAB didn't exist in 2.4.
|
|
don't overlap the wheel buttons. Patch from Alan Swanson (#968).
|
|
|
|
and can handle both mice and keyboards.
Convert this to UTF-8 again. The ChangeLog should be kept in UTF-8.
|
