I think I wasn’t clear in my explanation. I don’t think webCoRE is the issue.
Let’s assume that the following scenario takes place after the button has been installed and pressed as well as held, at least once. (This makes the current pushed and held values, both set to 1, or more).
So, now to create a trigger, I can use any combination of values or changes in values, provided by
Do note that the values of each of these attributes persist. So before I push the button, the value of pushed is 1. After I push the button once, the value is still 1. The only trigger I can use is to see if the
buttonReleased value changed (and then to look at the pushed value to determine the number of clicks).
With held, I don’t have such a liberty. The value of held, like pushed is still 1, both before and after holding the button. But here
buttonReleased, though a valid trigger, cannot tell me if the update in its value was because of a hold or a push. So technically, I can only intercept holds also as pushes only, in webCoRE.
Only solution I can think of is to have a
buttonHoldReleased or something similar, which updates only for a hold.
Again, I do not miss the lack of a valid trigger for hold at all. The handler works perfectly and now I have 5 different button press scenarios to chose from, unlike the limited options while I was on ST, thanks to you!