On Wed, Dec 15, 2010 at 04:24:40PM -0500, Chase Douglas wrote: > > Is this custom code or in upstream (are you talking about > > inside_active_area logic?)? I'm not sure why your seeing a jump if > > its being discarded. There is a chance that something related to this > > discard logic is defeating the other logic that handles jumps caused > > during finger transitions. > > In Ubuntu 10.10 I think we are using an in-house patched hack. It was > necessary for an Dell Minis, which was a paid OEM services project, so > we needed a fix ASAP at the time. I believe xf86-input-synaptics has an > option for this now, so we'll probably transition whenever someone gets > a chance to take another look. It may be something that would be handled > better by the upstream logic. When I get a chance I'll try the upstream > logic instead. mostly identical logic, but the Ubuntu patches only covered the bottom edge (MovementBottomEdge option, IIRC). The upstream version covers all four edges with AreaLeftEdge and friends. recent X servers also support a percentage as option, so instead of the hardcoded value for the edge, you can say Option "AreaBottomEdge" "20%" I've had a few attempts to fix this touchpad to work slighlty better but the box died on me before I could finish it. Feel free to send me one of these machines if you want it fixed, it's been bugging me for ages :) Cheers, Peter -- 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
