Ticket #4388 (open feature)
slider range option should work with more than two handles
| Reported by: | vitch | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.11.0 |
| Component: | ui.slider | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
Currently the range option in ui.slider doesn't work where there are more than two handles (in fact, it resets the values passed in so they both equal values[0]).
For my current use case the user should be able to select a range including a mid value (they are selecting a "typical", "min" and "max" size).
I propose that you should be able to have a range slider with more than two handles. In the simplist case it can be assumed that the first handle is the bottom of the range and the last handle is the top of the range. This will cover my use-case. I can also see a possible requirement for more complex ranges where the user could specify which handles represented ranges.
Attachments
Change History
Changed 4 years ago by vitch
-
attachment
ui.slider.4388.diff
added
comment:1 Changed 4 years ago by vitch
The attached patch seems to work for me. It may need more careful testing to check it works in all circumstances though. I was unable to figure out how the animate parameter was meant to work so I couldn't test that the logic worked there but I shouldn't have disturbed anything.
There was also some unused variables (vp0 and vp1) which I removed and I simplifed a little of the code by calcualing some local variables outside a loop.
comment:2 Changed 4 years ago by vitch
Demo page including patched slider:
http://www.kelvinluck.com/assets/jquery/ui-slider/slider_test.html
comment:4 Changed 4 years ago by joern.zaefferer
- Milestone changed from TBD to 1.8
Patch needs testing.
comment:6 Changed 2 years ago by NickHeiner
I implemented my own version of this before realizing that it had already been done here. It lets the user specify values for as many sliders as he wants, and set a CSS class for each range. Is it worth it to fork and send a pull request, or will the project probably go with the code that's already posted here?


Patch including fix for #4388