Reliable Button Release Check
grissler
Posts: 3
Has anybody come up with a way to reliably check whether a BUTTON RELEASE has been missed. I have had instances, usually with volume control, where the volume runs away because a Button Release is missed, probably due to a network issue or TP falling offline. I used to put an OFFLINE event that killed the IR, but that is still not 100% since I experimented and determined that it takes the processor around 30seconds to detemine that the TP has fallen offline, and by then it is too late.
0
Comments
For non-repeating buttons, we wait to see it passes into the HOLD condition, take our hold action if any, and force the release, as nothing more can happen that we care about anyway. If there is no unique action on HOLD, we take the release action and force the release. No more problems with this since we made this behavior....
Thanks John. I was already forcing the release on the Hold after a certain time. Didn't know if there was a better way.
Here is HOLD handler you can add to your button events for volume control. If the button is held down for more than three seconds a release will be forced.