Honestly, my issues are minimal in regards to the tap-to-click activating during
typing. If I'm typing in bed or at a awkward angle exacerbates it, but it's not
a huge issue. "Edge Zones" might be just the ticket. I always found the
syndaemon a bit odd, anyway, and had to play with the timing to make it feel
like it worked correctly.
I'll keep an eye out for your future posts and report any (and then when I went
to type anomalies, the tap-to-click got me, even though I'm not at an odd angle)
anomalies. So, parenthetically, edge zones might be the ticket! :D
On 12/5/17 5:23 PM, Ulf Brosziewski wrote:
Up to now, I have only vaguely considered that, and there are
some other things pending. However, if many users will be
missing that option, my priorities might change ;-) Would
"edge areas" be an alternative for you? synaptics(4) has an
option for defining edge zones. A touch that starts there does
not trigger pointer movement, tapping, and scrolling as long as
it hasn't left the area. The input driver in wsmouse(4) has a
similar mechanism, what's missing up to now is a decent way to
configure it, but it can be done, and it might be a way to mitigate
the effects of accidental touches. Of course, whether it could
help in your case depends on your habits.
On 12/06/2017 12:17 AM, Base Pr1me wrote:
Are there plans to have a solution to halt the touchpad when typing is
occurring, similar to what syndaemon does? Otherwise, the driver works fine
for me on ThinkPad T470s.
On Tue, Dec 5, 2017 at 3:59 PM, Ulf Brosziewski <ulf.brosziew...@t-online.de
wrote:
If you're following -current, or if you upgrade your system with the
next or a future snapshot, please note that the default setup for
touchpads in X will change.
X will select ws(4) instead of synaptics(4) as default driver. In a
configuration with ws, touchpad-specific input processing is done by
wsmouse(4). Touchpad configuration parameters are made available in
wsconsctl(4), see
https://marc.info/?l=openbsd-misc&m=150153498920367&w=2
for some hints (the wsmouse man page is not up to date yet).
Using synaptics(4) as input driver is still possible, it will require
a custom xorg.conf file. If you already have such a file - which
overrides the default -, please consider giving ws a try, and help
us by reporting problems if it doesn't work for you.
