On Wed, Jun 28, 2023 at 12:03:41AM +0200, Ulf Brosziewski wrote:
> This version of the diff adds a wsconsctl field, named "mouse.tp.
> mtbuttons", and an update to the wsmouse.4 page.  Apart from that, it
> contains only stylistic changes.
> 
> The new wsconsctl field is just a boolean, I don't think that it would
> make sense to include the distance filter in the configuration options.
> However, if a default value is derived from the length of the touchpad
> diagonal, it might be too high for over-sized touchpads.  If that turns
> out to be a problem, the proper place to fix it is the hardware driver.
> 
> OK?
> 

hi.

one note about the doc:

> Index: src/share/man/man4/wsmouse.4
> ===================================================================
> RCS file: /cvs/src/share/man/man4/wsmouse.4,v
> retrieving revision 1.22
> diff -u -p -r1.22 wsmouse.4
> --- src/share/man/man4/wsmouse.4      4 Mar 2021 17:03:42 -0000       1.22
> +++ src/share/man/man4/wsmouse.4      27 Jun 2023 18:54:31 -0000
> @@ -106,6 +106,10 @@ If, within a short time interval, a seco
>  mapped to a left-button click, the button-up event is not issued
>  until that touch ends
>  .Pq Dq tap-and-drag .
> +.It Cm mouse.tp.mtbuttons
> +This feature is supported from some clickpads.
> +If enabled, two-finger clicks - with the fingers side by side - generate
> +left-button events, three-finger clicks generate middle-button events.

at a minimum, i'd put a semi-colon after "events", not a comma.

or you could join the two parts like this:

        ...generate left-button events, whilst three-finger clicks...

or more simple:

        ...generate left-button events, and three-finger clicks...

jmc

>  .It Cm mouse.tp.scaling
>  The value is a scale coefficient that is applied to the relative
>  coordinates.

Reply via email to