On 12/15/2010 03:41 PM, Chris Bagwell wrote: > I meant to mention: once your initial draft gets committed I would > love to help update it some. I specifically want to show two example > usage. 1) touchpad as 1 to 3 touchs occur and show special > considerations to ABS_* that apps should handle. 2) a touchscreen > that supports a pen as well and show how tool change (finger to pen) > should work. For both those examples, it would be interesting to > discuss how MT can be used concurrently (does pen in slot 0 and touch > in slot 1 make sense for example). This is the other main reason I wanted to make the document. Having a place where best practices are detailed will help future driver writers and hopefully reduce errors in evdev code usage. I'd love to see this added to the document. I do think that MT is complex enough that related documentation should be in multi-touch-protocol.txt, though. Anywhere I discussed MT in evdev-codes.txt I referred the reader to the other file. Henrik, does that sound good to you? > I think it will be invaluable to document this stuff for driver > writers and apps but I'm not sure yet what level needs to be enforced. That's the biggest issue I see right now. Do we want black and white specificity? For example, using terms like "must" and "may not" etc. Or do we want the document to merely hold best practices while not proscribing exact details? I think even with exact details we can loosen them if needed, but that has its own can of worms. Dmitry, what are your thoughts on this? Thanks, -- Chase -- 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
