Peter Hutterer wrote: [...] > > To clarify: the MT_TOUCH_MAJOR is to track a touchpoint over time, and the > BLOB_ID to compile a arbitrarily shaped touchpoint within the same event? MT_TOUCH_MAJOR is the major size of the touching object, or "pressure" in case the size of the approaching object (MT_WIDTH_MAJOR) is not available to compare the size to. The touch and position packets are sent to the multitouch X driver, where the actual finger tracking takes place. Thanks for the chance to clarify this. > Would it make sense to allow specification of a blob as bit/bytemask? There > are a few devices that can do detection of multi-color non-rectangular > touchpoints, especially camera-based systems. Limiting these to a sequence of > rectangles means dropping information that may be useful for certain tasks > (e.g. fingerprint detection). > OTOH, a rectangle as bounding box with an accompanying (optional) bytemask can > pass this data on to prospective clients. Very interesting idea, although I believe it is beyond the scope of the current patch. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
