On Fri, Dec 10, 2010 at 1:28 AM, Henrik Rydberg <rydberg@xxxxxxxxxxx> wrote: >> > >> So how do you propose userspace will use it? Obviously it will not help >> old dumb (ST) applications and new smart applications should understand >> MT protocol and thus do not need to pay much attention to ST events >> anyway. Apparently you have some new dumb userspace in mind here? > > > You are right, it is a dumb idea. Consider this one dropped. If anyone is working on clickpad support, they may want to keep this idea in mind. I guess I mean working on clickpads and with simple ST apps. If user clicks with one finger, I think currently that user expects dragging that one finger will move cursor still (click-and-drag). I'd think its more usable though to click with one finger and drag with the other. During this use case we need to switch pointer tracking from one finger to the other. Sending a new tracking ID is an easy way to inform apps about expected jump in values during switch. I thought of things like BTN_TOOL_FINGER=0; sync; BTN_TOOL_FINGER=1 but that looks like tapping is occurring. Anyways, as you suggestion, this can be solved by forcing apps to process MT events so not to big a deal long term. Chris -- 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
