As title. I've created a slider and am binding the "max" property to some value, that I obviously don't want to be able to go past.
However, the way the "interval" and "step" are configured results in you being able to slide past the maximum value in increments of "step", and the "value" property is then > max.
in this example, "max" = 1879. "interval" = 300, "step" = 150.
That looks like a bug alright.
You can work around it easily though. Create a custom property clampedValue on the slider and create an expression binding:
min({this.props.value}, {this.props.max})
Yea ended up doing pretty much that. Hope this can get fixed by IA though.
Yes, it would get messy if you had the same problem at both ends of the track.
Did you open a support ticket? That's the only guaranteed way to get a bug ticket by IA.
This has been identified as a bug and added to the list of bug tickets by IA