Rendering error when updating values

[Andres9713]

Hi, I am using your RangeSliderH object to define the actual and maximum frame rates at which a video is being rendered (on a separate canvas). I am updating the 'actual frame rate' value every 0.1 seconds with:
rateSlider.forceValues([actualRate, maxRate]])

The issue is that in a random subset of these updates, the previous location of the 'actualRate' datapoint does not get erased causing the current and past values to be displayed simultaneously:

Is there any way of preventing this from happening, or somehow forcing a cleanup of the widget after value updates? Thank you.

[Andres9713]

Sorry - this second comment isn't an 'issue' but a different question: is there any way of defining which of the two range 'handles' will be drawn on top? Basically, I would like to always keep the 'right' max-rate slider always on top, as this is the one the user needs to interact with - is there anyway of setting this property, permanently or otherwise? Thank you.

[harshvinay752]

Hi @Andres9713, thank you for using RangeSlider, and pointing out error in the code.

1. I will look into the "handle datapoint not getting erased" issue.
2. Regarding the next comment to have datapoint values always on top, I am not completely certain about your requirement. Can you please elaborate the same in more fluid detail.

[Andres9713]

Hi @harshvinay752 - thanks for looking into (1) above. About the second point: in my application one of the two markers (the red one above, which shows the maximum frame rate allowed) is adjustable by the user (if the other, green, one is moved, it just gets moved back). However, in situation when the 'actual' and 'max' rates are the same, which happens a lot, then the 'green' marker will often be on top of and occlude the red marker. The desired behavior is that the green (left) marker never occlude the red (right) marker - i.e. that the red marker always be 'on top'. Does this clarify my question? Is there any way of achieving this? Thank you.

[harshvinay752]

I am sorry @Andres9713 for such a super late reply, got occupied in something personal, I hope you could manage your work meanwhile. The current version doesn't support the feature you are asking. I shall add the feature soon in upcoming versions. Thanks for providing a feature request.