Actually, I was just trying to eliminate an exception so we can ship a release.
I agree that there could be a even smaller bead that doesn't track changes as you move the thumb. Something to do in the next release, IMO. But I also saw that I hadn't quite implemented the change correctly, so I've just pushed a better version. Thanks, -Alex On 6/6/17, 5:14 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >I see you've added code to handle binding / values changes to >RangeModel.as and RangeModelExtended.as. > >Is there any reason the value change code is not in another classes >called for instance ValueChangeRangeModel? It seem to me that this model >it trying to do more than one thing i.e. value changes and min/max/step >changes. > >As I user of this I may not be interested minor max changes and only >interested in value changes so shouldn't that be an optional feature? > >I’m just trying to understand why it’s seemingly OK to not follow PAYG >here. > >Thanks, >Justin
