Suggestion for implementing 'setLongReleasedDelay' about acebutton

[bxparks]

I've been mulling over this for a few days, and I think I understand what you are trying to do. The problem is that the current kEventLongReleased is not intended to mean to what you want it to mean.

The current kEventLongReleased event was a solution to a very specific problem, as described in Distinguishing Pressed and LongPressed: When the kEventReleased is suppressed to allow the differentiation between Pressed and LongPressed, we lose the kEventReleased from the LongPressed, so the kEventLongReleased was added to compensate.

Your version of kEventLongReleased is different. It is the symmetric equivalent of the kEventLongPressed, triggered when a button is released for a long duration. I never considered this to be an event, because by default, the buttons are considered to be in the Released state, and it did not seem that an event should be triggered without a specific human action.

If we were to implement your version of kEventLongReleased, then by symmetry, it would imply that we should implement a kEventRepeatReleased which triggers every 200 milliseconds in the Released state, in the same way that kEventRepeatPressed is triggered. I'm not sure that makes sense.

So I have a counter-suggestion: You are essentially using the LongPressed event to perform debouncing of your water level switch at a much larger timescale than the usual 20-50 milliseconds. You want to a debouncing at the level of 5-10 seconds. So instead of using LongPressed, is it possible to achieve your goals by using the normal kEventPressed and kEventReleased, but increase your setDebounceDelay(5000) instead?