![]() |
2010-11-29
, 05:43
|
Posts: 329 |
Thanked: 505 times |
Joined on Jul 2008
@ Israel
|
#32
|
![]() |
2010-11-29
, 12:51
|
Posts: 323 |
Thanked: 116 times |
Joined on Jul 2010
|
#33
|
![]() |
2010-11-30
, 14:44
|
|
Posts: 234 |
Thanked: 175 times |
Joined on Jun 2010
@ Genova (Italy)
|
#34
|
![]() |
2010-11-30
, 17:26
|
Posts: 256 |
Thanked: 92 times |
Joined on Oct 2010
|
#35
|
![]() |
2010-11-30
, 17:52
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#36
|
x1 x2 -------------------------------------------- | o x | y1 | | | x o | y2 --------------------------------------------
![]() |
2010-11-30
, 18:02
|
Posts: 256 |
Thanked: 92 times |
Joined on Oct 2010
|
#37
|
In the current implementation of resistive screens there are two films one with horizontal and one with vertical "cables". When they touch each other, there is current at the end of those cables, just off the screen. Correct me if I am wrong.
Theoretically, such a screen cannot support multitouch because when you touch two points, there are 2 horizontal and 2 vertical points that get current (except if the touches are aligned on one axis)
The question is: who interpolates the touch points and produces the midpoint, the controller or the software? Can we tap into the controller fw? If we get those 4 coordinates, then we can narrow down the possible touch points to 4. Perfectly enough for all common multitouch gestures.
o --> real touch pointsCode:x1 x2 -------------------------------------------- | o x | y1 | | | x o | y2 --------------------------------------------
x --> possible touch points
![]() |
2010-12-01
, 00:42
|
Posts: 323 |
Thanked: 116 times |
Joined on Jul 2010
|
#38
|
if you have multiple signals supporting multi touch you need no emulation(and in this case a x driver can help).
if you emulate, you interpret a single signal, and simulate some usecases by giving some sequences of signals special meaning(->gestures). but this is not that easy for a gesture may collide with other usecases.
![]() |
2010-12-01
, 02:28
|
Posts: 256 |
Thanked: 92 times |
Joined on Oct 2010
|
#39
|
I think that a multi-touch x-driver could be useful also for emulating.
A multitouch driver also treats single touch events.
We could write a program that reads the events from the x-driver and writes back to the x-driver multi-touch events, when a specific combination of single touch events happens.
If we want to do this, the x-driver has to understand multi-touch events.
The Following User Says Thank You to lunat For This Useful Post: | ||
![]() |
2010-12-01
, 17:42
|
Posts: 323 |
Thanked: 116 times |
Joined on Jul 2010
|
#40
|
![]() |
Tags |
failthread, got search?, hardware limit, search much? |
Thread Tools | |
|
I'm guessing new drivers might be needed.
Does anybody know how to get this to work?