Possible wrong description in TouchPin.md about docs HOT 6 CLOSED

According to ffbf543, the correct description might be:

sets threshold to x, which will get smaller by touching the pin. In the driver a sensor value beneath that threshold, will trigger a button touch.

@Staars
Can you say anything about this?

from docs.

It’s been awhile that I played with the touch pins.
Yes, this looks like a copy-paste-error, but I am not sure, if my initial implementation was altered later on.
You can simply test the calibration process on the console. The initial idea was indeed to set the threshold value with TouchThres for a touch button.
I must take a look at the code, if things have changed …

from docs.

… and indeed, TouchNum was removed.
I guess, that Theo did some testings and found, that sensing the value of the touch pins over multiple loops, did not justify the resulting lag for the benefit of filtering out spikes. It is possible, that these sensing errors are less frequent with the newer SDK, than I did see when I did my initial testing.
Anyway, this command is gone and the touch button is a bit faster now, although measuring is technically not super quick.

from docs.

Thanks for clarifying.

Do you intend to edit the page?
Or should I create a PR to remove the command from the docs?

from docs.

I am sorry that it took so long. Should be correct now.

from docs.

Great. Thanks.

Just for protocol.
It is this Commit: 117d6dd

from docs.