Bug 24713 - drag lock not working well
Summary: drag lock not working well
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/evdev (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Peter Hutterer
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-24 11:06 UTC by Tom Horsley
Modified: 2009-11-01 20:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Tom Horsley 2009-10-24 11:06:23 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=524428

is my Fedora 12 bug report on this, but I suspect it is an upstream
problem, so I thought I should report it here as well.

If I try to make button 8 a drag lock for button 1, the results are
the wild and wacky results described in the redhat bugzilla above.

If I try to make button 8 a "universal" drag lock, using

xinput set-int-prop \
       'Kensington      Kensington Expert Mouse' \
       'Evdev Drag Lock Buttons' 8 8

It works better, but I have to click 8 then 1 to get out of the drag lock
as well as to get into it (which seems silly - I'd think that just click 1
or click 8 by itself would end the drag lock).

I'm still forced to disable evdev and go back to the old way of defining
drag lock to get my mouse in a usable state.
Comment 1 Peter Hutterer 2009-11-01 20:46:25 UTC
Thanks, indexing in the property handler was wrong and the numbers weren't assigned to the right buttons.

Fix pushed as 11669d82790fd7c94c44c0d487d3fa5e203528e9, at least for the multiple drag-lock button issue.

The other issue requires a bit more subtle changes to make sure we release the right buttons. Please file a new bug and add it to Bug 16699 (evdev feature request tracker). Note that the backlog is pretty bad at the moment, so it's probably best if you try to implement the feature yourself.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.