help: Can't get touch capabilities with "LayerManagerControl get input device default capabilities"

이양우 YangWoo.lee at hyundai-autron.com
Fri Aug 18 03:13:41 EDT 2017


I saw below guide in genivi wiki.
I can handle it separately now.

ATTRS{name}=="<sysfs name of the device with volume buttons>", ENV{WL_SEAT}="seat_volume"
ATTRS{name}=="<sysfs name of the device with conversation buttons>", ENV{WL_SEAT}="seat_conversation"
Second, input acceptance of Media Player and Telephone application are modified for the desired behaviour:
$ /usr/bin/LayerManagerControl set surface 100 input acceptance to seat_volume
$ /usr/bin/LayerManagerControl set surface 200 input acceptance to seat_volume,seat_conversation

Thank you.

-----Original Message-----
From: 이양우 [mailto:YangWoo.lee at hyundai-autron.com] 
Sent: Friday, August 18, 2017 3:51 PM
To: 'genivi-ivi-layer-management at lists.genivi.org'
Subject: RE: help: Can't get touch capabilities with "LayerManagerControl get input device default capabilities"

Hello.

Below issue was caused by additional string of "seat" value.
I used seatX in udev rules for touch devices.(E.g: seat1, seat2).
I looked up code for wayland-ivi-extension and Weston.
It seems look just "seat" string. right?
After change to "seat" from seatX, I can test touch now.

But I don't know how do I identify a multi seat in this case?

Thank you.

-----Original Message-----
From: 이양우 [mailto:YangWoo.lee at hyundai-autron.com] 
Sent: Friday, August 18, 2017 9:32 AM
To: 'genivi-ivi-layer-management at lists.genivi.org'
Subject: help: Can't get touch capabilities with "LayerManagerControl get input device default capabilities"

Hello

I'm doing test input device in ivi-shell with guide page. https://at.projects.genivi.org/wiki/display/WIE/10.+Getting+Started+with+new+Input+Handling+APIs
When I command, "LayerManagerControl get input device default capabilities", I can see only "pointer" capability.(My system has one mouse and two touch screen device) These input devices are already tested in desktop shell. For example touch devices are working separately on each screen. I could move Weston-flower application via touch.

This time, I want test touch input in ivi-shell. But touch capability is not coming.
Could you give me some advice or guide to resolve this problem?

Below is input device log of Weston startup:
[23:50:26.937] input device 'Atmel maXTouch Touchscreen', /dev/input/event0 is tagged by udev as: Touchscreen [23:50:26.937] input device 'Atmel maXTouch Touchscreen', /dev/input/event0 is a touch device [23:50:26.993] input device 'Atmel maXTouch Touchscreen', /dev/input/event1 is tagged by udev as: Touchscreen [23:50:26.993] input device 'Atmel maXTouch Touchscreen', /dev/input/event1 is a touch device [23:50:26.995] input device 'PixArt USB Optical Mouse', /dev/input/event2 is tagged by udev as: Mouse [23:50:26.995] Device 'PixArt USB Optical Mouse' set to 1000 DPI [23:50:26.995] input device 'PixArt USB Optical Mouse', /dev/input/event2 is a pointer caps ...
...
[23:50:27.103] Loading module '/usr/lib/weston/ivi-shell.so'
[23:50:27.105] launching '/usr/libexec/weston-keyboard'
[23:50:27.107] Loading module '/usr/lib/weston/ivi-controller.so'
[23:50:27.111] Loading module '/usr/lib/weston/ivi-input-controller.so'
[23:50:27.111] ivi-input-controller module loaded successfully!

root at linux:~# LayerManagerControl get input device default capabilities pointer




More information about the genivi-ivi-layer-management mailing list