lp://staging/~oif-team/frame/semi-mt-addons

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~oif-team/frame/semi-mt-add-touches at revision 36

Chase Douglas (community): Approve on 2011-04-26

Diff: 76 lines (+30/-22)

1 file modified

src/frame.c (+30/-22)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

36. By Henrik Rydberg on 2011-04-26

Additional corrections

In the branch, active is not set in one place, and the identifier
range can wrap, causing duplicate use. This patch corrects those
issues, and breaks out the setting of semi-mt touches into its
own function.

Signed-off-by: Henrik Rydberg <email address hidden>

35. By Chase Douglas on 2011-04-25

Clean up semi-mt touch count logic

By watching for BTN_TOUCH == 0 we can drop any logic handling for when
other semi-mt touch count events are sent with value 0.

34. By Chase Douglas on 2011-04-13

Set the touch ID half way around the ID range to be safe

33. By Chase Douglas on 2011-04-13

Provide the range of touch IDs and decouple ID from touch active state

The kernel provides a range of touch IDs for each device, and XI 2.1 will
have its own range as well. The tracking ID from the kernel is set to -1
when the touch goes inactive, but -1 (as an unsigned int) is a valid
value for XI 2.1. To make things work in both environments, the tracking
ID range is provided in the touch surface, and the active state has been
decoupled from the tracking ID value. The backend (mtdev or XI 2.1) must
now set the active value of the touch contact.

Also, to provide for the full range of XI 2.1 touch IDs, the ID value has
been changed to unsigned int.

32. By Chase Douglas on 2011-04-04

Split out EV_KEY handling and add support for BTN_TOOL_FINGER

31. By Chase Douglas on 2011-04-01

Set the active number of touches on semi-mt devices

Use the evdev semi-mt BTN_TOOL_*TAP events to set the active number of
touches on these types of devices.

30. By Chase Douglas on 2011-04-01

Add additional contacts for semi-mt devices

Semi-multitouch devices provide a bounding box in the first two touch
contacts and a number of touches within the bounding box. This change
keeps the first two touch contacts as the bounding box and then adds more
touches at the center of the box as needed to match the total number of
touches on the device.

The tracking ID is set to the first touchs' tracking ID minus 1 (skipping
over the invalid ID of -1). This ensures a unique tracking ID unless the
frame continues for 2^32 touches.

29. By Henrik Rydberg on 2011-03-15

Release version 1.1.2

Signed-off-by: Henrik Rydberg <email address hidden>

28. By Henrik Rydberg on 2011-03-15

Allow replay of device data through utouch-frame

This patch adds replay capabilities to test-mtdev.
If the specified device points to a valid evemu file,
the device properties will be extracted from that file
instead. Any appended event data will be replayed in
realtime. In practise, test-mtdev can be executed with
a test file.

Signed-off-by: Henrik Rydberg <email address hidden>

27. By Stephen M. Webb on 2011-03-15

Added a dependency check on xorg-server-dev when building with xi2 support.