<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Button areas on Lenovo Thinkpad W540" href="https://bugs.freedesktop.org/show_bug.cgi?id=99212#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Button areas on Lenovo Thinkpad W540" href="https://bugs.freedesktop.org/show_bug.cgi?id=99212">bug 99212</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>(In reply to Markus Schmidt from <a href="show_bug.cgi?id=99212#c5">comment #5</a>) > To me it seems that there's the button area and there is the touchpad area. > Switching from button area to touchpad area while the finger is touching the > surface prevents from the default touchpad behavior and is simply doing > nothing while swiping/clicking. The other way around (swiping from touch to > button) the button area seems to be ignored and is used like the touchpad > area. Both behaviors will last until one lifts the finger for a short amount > of time after the movement which seems to "reset" the zones. yep, it is intended behaviour to ignore the buttons when moving up - this increases the effective size of the touchpad area. I didn't realise that physical clicks were ignored when coming out of the top button area though. > Using the touchpad area as left click button unfortunately is not the same > as having it configured like a "real" button since it allows movement of the > pointer. So moving the pointer with the trackpoint where the click shall > appear and then moving the thumb to the left click position will move the > pointer a few pixels, too. This wouldn't be of a bigger problem for average > desktop use but me as a graphic designer is depending on pixel-precise > movement/clicks. hmm, this shouldn't happen, palm detection is active while the trackpoint is in use but I suspect your problem is that the click comes after the palm detection expired (the timeout is quite short). Exposing the full button configuration is something I'm very hesitant to expose, especially for what is now 3 year old hardware. Plus, options fix it on exactly one machine and then spread like an STD across forums, half the time without the users knowing what they actually set. So I'm looking for something that improves the touchpad for every user with a simple update. there are a few options we have here: we could make the buttons bigger while the trackpoint is in use and for longer afterwards. This would avoid the issue with pointer movement but may still have the left button out of reach for you. And from what I gather, the issue isn't so much that you're missing the middle/right button areas but rather that you can't left-click (without pointer movement) below those buttons - that's really what you need, right? If so, then extending the timeout to include most of the northern part of the touchpad for palm detection for longer should fix that. It's not the same as your configuration (buttons would remain the same size) but you can now click below them to trigger left-clicks.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>