Yes, I know all about that, I can reboot and get the default back. I
don't want to reboot. I want the default back now. Who thinks a
setting that magically changes itself but provides no way to change
back is a good idea?
What burns me is if the emulate code didn't work right away, I would
notice and do something to fix it. But I've had this particular X
session up for at least a day now. I've been left and right clicking
to emulate the middle button all day long. Now X has suddenly
decided, hey, I bet all those middle clicks you made for the past 24
hours were a mistake, let me turn that off for you. Wrong!
Switching to a text console and back has not resolved the problem for
me. I didn't know that was supposed to work, but now that two people
have told me about it, I can announce I tried it without success.
Honestly, I suspect some incantation of xinput should resolve this,
but fuck if I know how to use this thing.
> xinput --list
+ Virtual core pointer id=2 [master pointer (3)]
| + Virtual core XTEST pointer id=4 [slave pointer (2)]
| + /dev/wsmouse1 id=7 [slave pointer (2)]
| + /dev/wsmouse id=8 [slave pointer (2)]
+ Virtual core keyboard id=3 [master keyboard (2)]
+ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
+ /dev/wskbd id=6 [slave keyboard (3)]
> xinput --list-props 8
Device '/dev/wsmouse':
Device Enabled (114): 1
Coordinate Transformation Matrix (116): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (226): 0
Device Accel Constant Deceleration (227): 1.000000
Device Accel Adaptive Deceleration (228): 1.000000
Device Accel Velocity Scaling (229): 10.000000
WS Pointer Middle Button Emulation (232): 2
WS Pointer Middle Button Timeout (233): 50
WS Pointer Wheel Emulation (234): 0
WS Pointer Wheel Emulation Axes (235): 0, 0, 4, 5
WS Pointer Wheel Emulation Inertia (236): 10
WS Pointer Wheel Emulation Timeout (237): 200
WS Pointer Wheel Emulation Button (238): 4
> xinput --list-props 2
Device 'Virtual core pointer':
Device Enabled (114): 1
Coordinate Transformation Matrix (116): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
So my core pointer has no properties. wsmouse already has WS Pointer
Middle Button Emulation set to 2. Maybe I should turn it up to 11?
Why are there wsmouse and wsmouse1 devices anyway? I thought wsmouse
was supposed to mux the numbered devices.
Is the "Mouse Middle Button Emulation" property different? Which
pointer do I set it on? Should I use the 8, 16, or 32 format? If I
am supposed to set it, why doesn't it appear in the list of properties
I can set, as per --list-props?
On Thu, Aug 23, 2012 at 14:20, David Diggles wrote:
> man mouse
>
> Option "Emulate3Buttons" "boolean"
> Enable/disable the emulation of the third (middle) mouse button
> for mice which only have two physical buttons. The third
> button
> is emulated by pressing both buttons simultaneously. Default:
> on, until a press of a physical button 3 is detected.
>
> On Thu, Aug 23, 2012 at 12:08:20AM -0400, Ted Unangst wrote:
>> I have a laptop with two buttons. To middle click, I click both at
>> the same time.
>>
>> Until, in a fit of stupidity, I plugged in a USB mouse and clicked the
>> real middle button. Now, the middle button emulation has oh so
>> helpfully disabled itself. Except I'm no longer using the mouse.
>>
>> I'm not sure if I should file a bug report or just ask for help.
>> I think it's kind of stupid to disable emulation, precisely because of
>> the situation I find myself in. But never mind that, how do I turn
>> emulation back on?
