[Ubuntu-x-swat] [Bug 767315] Re: xinput 2 Coordinate Transformation Matrix not affecting all events

2011-07-08 Thread Anisse Astier
Interestingly, the original question

 xinput 2 Coordinate Transformation Matrix not affecting all events

... would refer to device id 2, which would be the master (Virtual core 
pointer id=2 [master pointer (3)]) ...

No it wouldn't. I was refering to XInput, protocol version 2, to say that this 
property is an XInput property, and not a driver (evdev…) property, like 'Evdev 
Axes Swap'; which is broken in ubuntu, but utouch team told me migrate to the 
new 'Coordinate Transformation Matrix', which also happen to be broken.
So, I was indeed referring to device 9 (see xinput.txt)


 The problem for me is that I can get my device (touchscreen) rotated with 
 `xinput set-float-prop...` if I get its id right - but I'd like to transform
 mouse AND touchscreen AND touchpad at the same time with one command, so I'm
 trying to change Coordinate Transformation Matrix of the master […]

I'm afraid this is another problem, I'd even say a it's a feature
request. For now you just do a for loop on all devices and apply the
appropriate coordinate transformation matrix.

For example (untested) :
ROTATION=left
MATRIX=0 -1 1 1 0 0 0 0 1
xrandr -o $ROTATION
for dev in $(xinput list |grep slave  pointer | sed -e 's/^.*id=//' | awk 
'{print $1}')
do
   xinput set-float-prop $dev Coordinate Transformation Matrix $MATRIX
done

Cheers :-)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/767315

Title:
  xinput 2 Coordinate Transformation Matrix not affecting all events

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/767315/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 767315] [NEW] xinput 2 Coordinate Transformation Matrix not affecting all events

2011-04-20 Thread Anisse Astier
Public bug reported:

After rotating the screen with xrandr -o left and rotating the input device 
with:
xinput set-float-prop 9 Coordinate Transformation Matrix  0 -1 1 1 0 0 0 0 1

I still noticed some events being sent, but not transformed.
In the sample below, see the jump from y coordinates ~1040 to ~205 and the back 
(I almost didn't move my finger):
$ xinput test-xi2
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ eGalax Inc. USB TouchController   id=9[slave  pointer  (2)]
⎜   ↳ HID 04f3:0103 id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ HID 04f3:0103 id=10   [slave  keyboard (3)]
↳ USB 2.0 Cameraid=12   [slave  keyboard (3)]
↳ Asus Laptop extra buttons id=13   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
EVENT type 9 (FocusIn)
device: 3 (3)
windows: root 0xad event 0x261 child 0x0
mode: NotifyNormal (detail NotifyNonlinear)
flags:  [same screen]
buttons:
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
root x/y:  590.00 / 1050.00
event x/y: 523.00 / 997.00

EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 598.83/1065.11
event: 598.83/1041.11
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
1: 25544.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 598.83/1065.11
event: 598.83/1041.11
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
1: 25544.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 594.71/227.50
event: 594.71/203.50
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
0: 25368.00
1: 5456.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 593.96/226.83
event: 593.96/202.83
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
0: 25336.00
1: 5440.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 592.46/226.17
event: 592.46/202.17
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
0: 25272.00
1: 5424.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 591.33/225.50
event: 591.33/201.50
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
0: 25224.00
1: 5408.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 590.21/224.83
event: 590.21/200.83
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
0: 25176.00
1: 5392.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 590.21/1049.77
event: 590.21/1025.77
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
1: 25176.00
windows: root 0xad event 0x261 child 0x0
EVENT type 6 (Motion)
device: 2 (9)
detail: 0
flags: Pointer Emulated
root: 590.21/1049.77
event: 590.21/1025.77
buttons: 1
modifiers: locked 0 latched 0 base 0 effective: 0
group: locked 0 latched 0 base 0 effective: 0
valuators:
1: 25176.00
windows: root 0xad event 0x261 child 0x0

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-core 2:1.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2

[Ubuntu-x-swat] [Bug 767315] Re: xinput 2 Coordinate Transformation Matrix not affecting all events

2011-04-20 Thread Anisse Astier
-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/767315

Title:
  xinput 2 Coordinate Transformation Matrix not affecting all events

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)

2010-04-14 Thread Anisse Astier
I ported nw-fermi to 2.6.33.2 in the attached patch; just a few kfifo
API adjustments, and I put the 007a device by default.

For those using nw-fermi, did you calibrate the screen? Did you modify
your xorg.conf?


** Patch added: Patch for nw-fermi on 2.6.33
   http://launchpadlibrarian.net/44150544/nw-fermi-2.6.33.patch

-- 
Handling NextWindow Touchscreen (multitouch)
https://bugs.launchpad.net/bugs/379313
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp