[21:20:22]  whot: we ignore the core pointer [21:20:32]  hadess: do we? [21:20:40]  hadess: i thought we did both [21:20:42]  halfline: in my patches, yes :) [21:20:49]  oh okay [21:20:50]  hadess: ok, in that case, look at the g-s-d touchpad patch. when you're setting the button mpaping for the touchpad, set the tap-button as 3-1-2 [21:21:10]  this way tapping is posted as 3, then mapped again to 1 by the server [21:21:12]  ***  federico has left chat #fedora-desktop (Leaving.). [21:21:37]  whot: won't that conflict? [21:21:47]  whot: does the tap button show up as a different button than the touchpad mouse button? [21:22:01]  halfline: no, that's the problem [21:22:33]  whot: is it feasible to make it do that? [21:22:37]  halfline: all the server knows is you just pressed button 1 (which is mapped to 3 in left-handed) [21:22:44]  not for f11 [21:22:50]  right [21:22:59]  i just mean at some point [21:23:15]  the easiest is to check whether we're right or left-handed in set_tap_to_click, and set the button mapping appropriately [21:23:33]  cool [21:24:14]  where few == roughly 100% of applications [21:24:53]  as in time vs. need [21:25:41]  arf, yes, you're right [21:26:24]  whot: so i'm a little confused. why don't we make the tap physical button 6 [21:26:36]  whot: and map it to logical button 0 [21:26:37]  ? [21:26:56]  along with physical button 1 [21:27:20]  halfline: oh, that would work if X allowed you to map two buttons to the same number. which it doesn't. [21:27:28]  ah ha [21:27:35]  halfline: well, in core anyway [21:27:46]  wait. I think I actually fixed that in 1.6 [21:29:44]  ooh. it is fixed in XI 1.5 [21:31:36]  well that's good [21:32:21]  the neat thing about this is, i think we only ever swap 1 and 3 [21:32:22]  ok, try xinput --set-button-map "device name" 1 2 3 4 5 6 7 8 9 1 11 12, and then synclient TapButton1=10 [21:32:32]  so if 6 is mapped to 0 then we won't ever try to change it for lefties [21:32:41]  6 is reserved though [21:32:57]  oh well whatever the next number is [21:33:07]  4/5 vert scroll, 6/7 horiz scroll, 8/9 back/forward seems to be the standard these days [21:33:41]  oh right, i was only thinking of vertical scroll, not horizontal (and i've never even heard of back/forward) [21:34:22]  hmm i wonder if we should be swapping the axes of those guys in ltr locales :-) [21:34:26]  halfline: if you have a mouse with more than 3 buttons, the side buttons have the back/forward functiality in firefox [21:34:34]  and it's all automagically too [21:34:37]  s/ltr/rtl/ [21:34:44]  hehe [21:34:55]  ***  xkahn has left chat #fedora-desktop (Read error: 131 (Connection reset by peer)). [21:35:32]  ***  xkahn (~xkahn@pool-71-174-240-233.bstnma.fios.verizon.net) has joined chat #fedora-desktop. [21:36:05]  ***  jclinton (~jclinton@65.28.69.86) has joined chat #fedora-desktop. [21:37:48]  whot: well, the buttons on _my_ mouse don't work like that [21:38:02]  that's unfortunate [21:38:22]  should've stayed quiet, now I have another bug to deal with... [21:38:41]  hadess: what's the button codes in xev? [21:38:54]  actually, that seems to work fine :) [21:39:01]  works for me too [21:39:14]  if i switch to left handed mode the tap stays as left click [21:39:30]  and the buttons under the pad get swapped [21:39:41]  what's button 10 for? [21:39:48]  hadess: tap [21:39:50]  i wish it popped up a window chooser [21:39:52]  i don't think it has a function [21:40:02]  hadess: xi2 xi2 xi2 xi2 :) [21:40:16]  gah i'm not doing compass [21:40:19]  * halfline goes off irc