No worries. Actually, allowThumbOverlap="false" is the default. For me, allowing thumb overlap would purly depend on the use case. My opinin is that it makes more sense to the user to not allow the right thumb to go past the left thumb and vice versa. but, IMHO. Good example.
-TH --- In [email protected], "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > FWIW, If I were building this for users, I'd still allow sliders to overlap > for ease-of-use purposes, but I'd fetch max and min on change rather than > every loop of the filter function ;-) > > -Josh > > On Thu, Aug 7, 2008 at 9:31 AM, Josh McDonald <[EMAIL PROTECTED]> wrote: > > > Coz it's a quick and nasty (but working) example, and I have zero knowledge > > about the finer details of the slider controls :) > > > > > > On Thu, Aug 7, 2008 at 9:28 AM, Tim Hoff <[EMAIL PROTECTED]> wrote: > > > >> Hey Josh, > >> > >> What's up with: > >> > >> return item.value >= > >> Math.min(priceSlider.values[0],priceSlider.values[1]) && > >> item.value <=Math.max(priceSlider.values[0],priceSlider.values [1]); > >> > >> You can avoid this by setting allowThumbOverlap="false". Then just use: > >> > >> return item.value >= priceSlider.values[0] && item.value > >> <=priceSlider.values[1); > >> > >> -TH > >> > >> > >> > > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] >
