You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Triple pressing acts as a double push instantly followed by a single press. Realistically this should still fall under control of the debouncing methods, given that's it's highly unlikely someone wants to action a double press and then a single press like that. Ideally, it should not register the 3rd press... so in other words, it should action the double press method and ignore the 3rd press (within the debounce period)
The text was updated successfully, but these errors were encountered:
Might be a "multiple press" event and a register to read the number of presses.
That would fit all situations, the proposed one by IAmOrion and perhaps somebody coding an Easter egg after ten presses :)
Hello,
In the version V2.1 i have fixed this issue.
After detecting a double push there is window of the same amount of the DPPERIOD where the button is not detected.
Hello,
In the version V2.1 i have fixed this issue.
After detecting a double push there is window of the same amount of the DPPERIOD where the button is not detected.
Do I have to upload a new firmware to the I2C encoder somehow? Or do I only need to update the library? I have the v2.0 board I believe
Triple pressing acts as a double push instantly followed by a single press. Realistically this should still fall under control of the debouncing methods, given that's it's highly unlikely someone wants to action a double press and then a single press like that. Ideally, it should not register the 3rd press... so in other words, it should action the double press method and ignore the 3rd press (within the debounce period)
The text was updated successfully, but these errors were encountered: