View Single Post
Old 11-16-2012, 04:55 PM   #15
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by h1uke View Post
just FYI. My impression that linux touchscreen device driver on PW cannot
convey 3- or more fingers tap messages.
I tried this many times while creating a rudimentary touchscreen support for Qt
on KPW, but with no luck.
On my PW:
Code:
# evtest -i /dev/input/event0
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "cyttsp"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
    Event code 333 (Tool Doubletap)
    Event code 334 (Tool Tripletap)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      0
      Min        0
      Max      758
    Event code 1 (Y)
      Value      0
      Min        0
      Max     1024
    Event code 47 (MT Slot)
      Value      0
      Min        0
      Max       15
    Event code 53 (MT X)
      Value      0
      Min        0
      Max      758
    Event code 54 (MT Y)
      Value      0
      Min        0
      Max     1024
    Event code 57 (MT Tracking ID)
      Value      0
      Min        0
      Max       16
Testing ... (interrupt to exit)
It claims to support "Tool Tripletap" (three fingers touching). However, while trying to cause that even, I could only create "Touch", "Toolfinger", and "Tool Doubletap" events -- no "Tool Tripletap":
Code:
Event: time 1353077577.779067, type 1 (Key), code 330 (Touch), value 0
Event: time 1353077577.779069, type 1 (Key), code 325 (ToolFinger), value 0
Event: time 1353077577.779070, type 1 (Key), code 333 (Tool Doubletap), value 0
I tried this on my K5 too:
Code:
]# evtest -i event3
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "zforce"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 0 (Reserved)
    Event code 1 (Esc)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
    Event code 333 (Tool Doubletap)
    Event code 334 (Tool Tripletap)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      0
      Min        0
      Max     4095
    Event code 1 (Y)
      Value      0
      Min        0
      Max     4095
    Event code 47 (MT Slot)
      Value      0
      Min        0
      Max        1
    Event code 53 (MT X)
      Value      0
      Min        0
      Max     4095
    Event code 54 (MT Y)
      Value      0
      Min        0
      Max     4095
    Event code 57 (MT Tracking ID)
      Value      0
      Min        0
      Max      255
Testing ... (interrupt to exit)
Surprisingly (or not), the K5 ALSO claims to support "Tool Tripletap", even though the Z-Force IR touchscreen is specified as only having 2-touch support.

Because the K5 and PW share a common 5.x code base, perhaps the PW touchscreen code is bound to the "lowest common denominator", and limited to the lesser K5 2-touch support (even if the capacitive touchscreen could support more simultaneous touch points).

Last edited by geekmaster; 11-16-2012 at 05:06 PM.
geekmaster is offline   Reply With Quote