Bugs/issues

[IAmOrion]

So I've been testing this on an RP2040 and also ESP32....

The Double Tap (click) never triggers, no matter how fast or slow I try tapping the screen, it only ever registers a SINGLE tap

Touch points is always 1 - I'm not entirely sure what this is supposed to do, but it's just always 1

Event - from the library comments I'm assuming this is meant to allow you to differentiate between touching and releasing but it just doesn't really work. when touching, it's 2, when I remove my finger after a swipe for example, 95% of the time it remains 2. Rarely it will show 1 which Is what I would expected when removing my finger / exiting the screen

This is a great start at a library, but it really isn't hugely useful in it's current state because of the inconsistencies etc

How does one deduce when an action has been completed RELIABLY? Again, Double Tap/Click is never recognised either

[KyleJewiss]

The library example works for me on my ESP32. I assume you have tested with this, but if not you can see a double tap will usually register a single click before than registering the double click.

To make it usable, I just check for the gesture interrupt, if its a single click I wait for a short period before than checking for the second. Idk if this is helpful for you, just thought I'd share my experience.

[georgemclaughlin]

The latest version 1.2.0 has a function to enable double click, it is not enabled by default.

Check out this example https://github.com/fbiego/CST816S/blob/main/examples/double_click/double_click.ino