getting reliable HOLD from Flic Button
I am building an app which requires the user to use a flic button to enter 1 of three states.
I am using click, double click and HOLD.
I have found that HOLD is not reliable. This is even true with the sample IOS app developed by FLIC.
single click and double click are reliable, however HOLD works maybe 75% of the time.
Is there any solution for this? or is this button really a 2 state ( click/double click) device.?
Any advice is welcome!!!
info 6 last edited by
Same problem here.
The Flic2 buttons are much less reliable then the Flic1.
Something to do with the hardware switch bouncing?
Some buttons works some other don't repsonde correctly to the 3 form of click.
andy.lundquist last edited by
This is a huge problem with all 6 of my brand new Flic buttons. The "HOLD" function either registers as a single click, or as multiple single clicks. This is an extremely frustrating issue that renders them practically useless for my application and seems like a major oversight.
I am pressing the button firmly. Also, I get the same issue with any of my flic 2 buttons.
Also, when hold stops working, the button usually has to sit idle for a few seconds before hold wil work again.
This is repeatable with your IOS sample app. Not my code.
I get single clicks instead of holds.
Hi. Do you get any other events instead of hold? For example some click or double click events. I'm thinking of if the physical switch isn't pressed enough to get contact.