Re: Using touchscreen with headless system

[Elias Bakken <elias bakken gmail com>]

Thanks a bunch Lionel, if you find the time to fix it, I will certainly be available for testing! If not, I might have to fix it myself in time for a Maker Fair coming up in a couple of weeks. Here is the output from evtest in case you need some reference data. It looks very similar to the already implemented touchpad I see: 

root thing:/usr/src/toggle/clutter# evtest /dev/input/event1 

Input driver version is 1.0.1

Input device ID: bus 0x3 vendor 0x3eb product 0x2118 version 0x111

Input device name: "Intelligent Agent CDC and Digitizer"

Supported events:

  Event type 0 (Sync)

  Event type 1 (Key)

    Event code 330 (Touch)

  Event type 3 (Absolute)

    Event code 0 (X)

      Value    894

      Min        0

      Max     4095

    Event code 1 (Y)

      Value    772

      Min        0

      Max     4095

    Event code 24 (Pressure)

      Value      0

      Min        0

      Max        1

    Event code 47 (?)

      Value      0

      Min        0

      Max        9

    Event code 53 (Position X)

      Value      0

      Min        0

      Max     4095

    Event code 54 (Position Y)

      Value      0

      Min        0

      Max     4095

    Event code 57 (Tracking ID)

      Value      0

      Min        0

      Max    65535

    Event code 58 (?)

      Value      0

      Min        0

      Max        1

Testing ... (interrupt to exit)

Event: time 946698841.225141, type 3 (Absolute), code 57 (Tracking ID), value 4095

Event: time 946698841.225141, type 3 (Absolute), code 53 (Position X), value 630

Event: time 946698841.225141, type 3 (Absolute), code 54 (Position Y), value 1236

Event: time 946698841.225141, type 3 (Absolute), code 58 (?), value 32

Event: time 946698841.225141, type 1 (Key), code 330 (Touch), value 1

Event: time 946698841.225141, type 3 (Absolute), code 0 (X), value 630

Event: time 946698841.225141, type 3 (Absolute), code 1 (Y), value 1236

Event: time 946698841.225141, type 3 (Absolute), code 24 (Pressure), value 32

Event: time 946698841.225141, -------------- Report Sync ------------

Event: time 946698841.230170, type 3 (Absolute), code 57 (Tracking ID), value -1

Event: time 946698841.230170, type 1 (Key), code 330 (Touch), value 0

Event: time 946698841.230170, type 3 (Absolute), code 24 (Pressure), value 0

Event: time 946698841.230170, -------------- Report Sync ------------

Event: time 946698841.240141, type 3 (Absolute), code 57 (Tracking ID), value 4096

Event: time 946698841.240141, type 3 (Absolute), code 58 (?), value 13

Event: time 946698841.240141, type 1 (Key), code 330 (Touch), value 1

Event: time 946698841.240141, type 3 (Absolute), code 24 (Pressure), value 13

Event: time 946698841.240141, -------------- Report Sync ------------

Event: time 946698841.245156, type 3 (Absolute), code 57 (Tracking ID), value -1

Event: time 946698841.245156, type 1 (Key), code 330 (Touch), value 0

Event: time 946698841.245156, type 3 (Absolute), code 24 (Pressure), value 0

Event: time 946698841.245156, -------------- Report Sync ------------

I would have gotten right on this had it not been for the problem of shading a Mash model as well. But, I'll start a new thread if I do not get anywhere with poking around.. 

On Fri, Jan 3, 2014 at 5:31 PM, Lionel Landwerlin <llandwerlin gmail com> wrote:

Ah!

That would be the same problem someone already pointed out.
There is no code to translate touch events codes from the evdev event format to Clutter's format.
It should be pretty straight forward to implement, but we kind of need someone (with the hardware to test it) to write that piece of code.

The piece of code you want to modify is around here :

https://git.gnome.org/browse/clutter/tree/clutter/evdev/clutter-device-manager-evdev.c?h=clutter-1.18#n550

Here is the kernel documentation to deal with input events :

https://www.kernel.org/doc/Documentation/input/multi-touch-protocol.txt

I might have a look at it this weekend, but not sure.

Cheers,

-
Lionel

On 03/01/14 16:06, Elias Bakken wrote:

Lionel, I have tried connecting "event" to the stage and also "gesture-begin" as a test without any luck. Based on your message now I also discovered "touch-event", which seemed promising, and also the "captured-event" but I was unable to get any output from that either..

I'm using Clutter 1.16 and I am on a headless system, not X nor Wayland, directly on the framebuffer. (BeagleBone Black)

On Fri, Jan 3, 2014 at 4:46 PM, Lionel Landwerlin <llandwerlin gmail com> wrote:

Hi Elias,

I had touch events to work on a touch screen laptop last month.

What signal are you connecting? Because touch events happens on a different signal from the one for mouse events.

What version of Clutter are you using?

Are you embedding Clutter into a Gtk window?

Cheers,

-
Lionel

On 03/01/14 15:38, Elias Bakken wrote:

Hi!
I'm trying to get some basic functionality going with a touch screen. The device seems to be working fine using evtest and X but when trying to connect a signal (event) to the stage, nothing happens. A normal mouse seems to be working fine. Looking at the list of devices coming from the DeviceManager, I see the touch screen is found and has type CLUTTER_TOUCHSCREEN_DEVICE and is enabled. The core pointer also lists both the mouse and the touch screen as slave devices.

Does anyone have any pointers (pun intended:) for this?

I'm using Python as a language binding.

--
Kind regards,
-Elias

_______________________________________________
clutter-list mailing list
clutter-list gnome org
https://mail.gnome.org/mailman/listinfo/clutter-list

--

Kind regards, 

-Elias

_______________________________________________
clutter-list mailing list
clutter-list gnome org
https://mail.gnome.org/mailman/listinfo/clutter-list

--

Kind regards, 

-Elias