TripleClick and higher counts

[wjcarpenter]

Is there already a way to implement detecting a TripleClick or other rapid-fire multi-clicks?

I was using a different library that provided a multi-click thing that would tell you how many clicks had happened (with the same sort of timing considerations as for AceButton DoubleClick). I used that to implement an infrequent UI item. I ran into other limitations in that other library and came back to AceButton. I'm wondering if I can salvage my TripleClick user experience in some reasonable way. I'm already using SingleClick and DoubleClick on that button for different things.

[wjcarpenter]

Ah, I see this comment in ButtonConfig.h:

    /**
     * Flag to suppress kEventReleased after a kEventDoubleClicked. A
     * kEventClicked is _always_ suppressed after a kEventDoubleClicked to
     * prevent generating 2 double-clicks if the user performed a triple-click.
     */
    static const FeatureFlagType kFeatureSuppressAfterDoubleClick = 0x20;

So, my hopes for TripleClick are raised. I'm still working through things to see if I can figure out how to realize it in some combination of AceButton and application code.

[bxparks]

I don't have plans to implement a TripleClicked event, because:

1. I don't use it, and
2. It will require a fair amount of design and testing, to make sure it doesn't interfere badly with Clicked and DoubleClicked events, and I don't have the motivation to spend that much effort, and
3. I no longer work on Arduino projects. Partially due to my frustrations with the Arduino dev tools and the Arduino API. I may come back to Arduino in the future. But given my other priorities, it may be at least 2 years.

You are welcome to implement it yourself, since you have the source code. You will have to add an additional delay parameter (e.g. kTripleClickDelay = 400), and add some kFeatureSuppressXxx flags, and figure out how to allow the user to distinguish between a kEventClicked event, a kEventDoubleClicked, and a kEventTripleClicked. One problem that I can immediately see extra delay that a TripleCilcked will cause to the Clicked event, since the code has to wait 800-1000 milliseconds to distinguish the 2 events. I suspect that testing will be important, because there may be a lot of edge cases.

[wjcarpenter]

Fair enough. (In the meantime, I have taken a different approach.)