Long button press to trigger an event

RE: Long button press to trigger an event

Tandon — Wed, 08 Jan 2020 14:37:17 GMT

https://github.com/NordicPlayground/nrf51-app-button-example/blob/master/main.c

This was also helpful

RE: Long button press to trigger an event

Heidi — Wed, 08 Jan 2020 09:39:41 GMT

Hi again!

It is my understanding that you want to differentiate between a long button press (a hold) and a short button press (a press), is that correct? If yes, the answer from Vidar in this thread provides an example for how to do this.

Let me know if that wasn't what you were looking for.

Best regards,

Heidi

RE: Long button press to trigger an event

Tandon — Wed, 08 Jan 2020 00:02:34 GMT

Heidi,

Your response has helped me a lot. I decided to go with button handler approach. However, I do have a query with that.

Upon a button press - I seem to be getting 2 events. My guess is from HighToLow and LowToHigh. There is, unfortunately, no RC filter in place that can help with this. Tweaking the BUTTON_DETECTION_DELAY has also not been of much help. Are there any other approaches that might help?

Is it possible for me to initialize GPIOTE_CONFIG_IN_SENSE_HITOLO and GPIOTE_CONFIG_IN_SENSE_LOTOHI, instead of a single GPIOTE_CONFIG_IN_SENSE_TOGGLE? Any direction or example would help me greatly.

In my application, I need to detect a hold and press. A hold is detected with an app timer, I believe.

Happy New Year and thanks in advance!

RE: Long button press to trigger an event

Heidi — Thu, 12 Dec 2019 17:32:11 GMT

Hi! I apologize for the slow response.

I'm going to assume you're asking about the difference between the Board Support Package (BSP) and the Button Handler. Please correct me if my assumption is wrong.

The BSP provides another layer of abstraction on top of the button handler, but it is mostly used for handling buttons in BLE examples, using the BSP BLE Button Module. If you are just writing a simple button handler, I would use the Button Handler library.

If you take a look at bsp.c, app_button.h is included in that. So it utilizes the functions in the button handler, but it provides another layer of abstraction.

Best regards,

Heidi