Just found the source of all phantom onTouchEnded calls I had, and it's in the commit in #162, which adds onTouchEnded call to every setRangePinsByValue call.
Any reason why we even need this? It triggers every time value range is set, and that's kind of a problem because I use onTouchEnded listener to distinguish user-made changes from programmatic value updates, but I can't use it because onTouchEnded is called on every value update no matter the source. It's the only setter method that calls this listener for no apparent reason.
Just found the source of all phantom onTouchEnded calls I had, and it's in the commit in #162, which adds
onTouchEndedcall to everysetRangePinsByValuecall. Any reason why we even need this? It triggers every time value range is set, and that's kind of a problem because I useonTouchEndedlistener to distinguish user-made changes from programmatic value updates, but I can't use it becauseonTouchEndedis called on every value update no matter the source. It's the only setter method that calls this listener for no apparent reason.