On 12/08/2010 11:23 AM, Henrik Rydberg wrote: >>>> I suggest merely renaming this to MT_TOOL_RECT to avoid confusion. > >> >> This is really the main point I wanted to make, even though it was >> hidden among other things :). Do you have thoughts here? > > > I think envelope works fine - it is easier to associate with a single point that > the notion of a rectangle. I thought we were talking specifically about two points? If I'm wrong, the following won't make any sense either :). There would be two slots with MT_TOOL_ENVELOPE set to 1. These define the two possible combinations of touch points. I can't see how this concept could be expanded any further than a rectangle without switcing to full MT, thus I think it would be clearer to define it as such. This all drives at the heart of the frustrations felt about evdev property naming and documentation. The envelope tool, as you've proposed, is only useful for defining rectangles. I think leaving it named envelope is just begging for misuse, just as BTN_TOOL_DOUBLETAP has been misused. Perhaps it will be clearer to me why you like the name envelope if I could read the formal documentation that would be merged along with the new property name. The documentation added by the patch just isn't enough to understand what it's for or how to use it, and the discussion so far hasn't left me with the feeling that MT_TOOL_ENVELOPE is the best name. -- 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
