<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - NEW: Proposal for mouse scroll wheel disabling while middle click is held."
href="https://bugs.freedesktop.org/show_bug.cgi?id=106286#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - NEW: Proposal for mouse scroll wheel disabling while middle click is held."
href="https://bugs.freedesktop.org/show_bug.cgi?id=106286">bug 106286</a>
from <span class="vcard"><a class="email" href="mailto:pyrosoma1@yahoo.ie" title="pyrosoma1@yahoo.ie">pyrosoma1@yahoo.ie</a>
</span></b>
<pre><span class="quote">>Yeah, but libinput isn't a project just for you</span >
Of course not, but any code added is contingent on the bug I submitted.
Therefore I am obligated to express my wishes explicitly. Responding in a
passive manner is unconstructive.
<span class="quote">>let's not have "nobody" or "everybody" arguments</span >
Fair enough, I completely understand. The 3 button modern mouse is surprisingly
standardised however. It's possible that someone could remap middle click and
become frustrated by the mouse's disabled wheel.
One way to deal with complaints would be to have the feature as an option, then
if no complaints are made after the dust settles have it as default.
Do you ever get wheel events before the BTN_MIDDLE click?
I do as I have removed the wheel detent to lessen rsi. It's a common failure
point though and happens to many similar models without intervention. the g502
has built in code to ignore wheel events when moving very slowly, which works
well. As I said, I find any motion to be easily compensated and any trade offs
of a sensitive wheel are worth it to me for the increased responsiveness. It's
only when I attempt to perform an action that difficulty results. I rise my
finger to the 12 o clock wheel position before clicking, this prevents wheel
events prior to the click.
I bought the g400s used so I do not know if the wheel had been software
modified. I doubt it supports such a mod as I attempted to remap dpi buttons
and it kept reverting to default.
I don't know how to check the udev property. In any event mouse specific fixes
are beating around the bush.
The mouse I am currently using is an io1.1 shell with a teensy 2.0 replacing
the mcu. I modified the source to disable the wheel from mouse3, that was how I
tested the proposal.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>