Ah- nice- that makes sense- changing it to values worked-
Now, is there a way to actually get the index of the handle that was
clicked on? short of just figuring it out based on the start value?
Thanks for all your help Richard,
Mike
On Jan 29, 8:22 pm, "Richard D. Worth" wrote:
> On Thu, Ja
On Thu, Jan 29, 2009 at 8:16 PM, m...@fonolo.com wrote:
>
> So I grabbed a copy of ui.slider and ui.core from trunk, and it does
> indeed fix the issue with clicking on the handle; it is now clickable,
> and it doesn't shift around.
Glad to hear it.
>
>
> BUT
>
> it seems when I have multiple
So I grabbed a copy of ui.slider and ui.core from trunk, and it does
indeed fix the issue with clicking on the handle; it is now clickable,
and it doesn't shift around.
BUT
it seems when I have multiple handles on a slider (using values:
[ array of integers ], but NOT using a range), while the h
Thanks Richard,
I tried both changing the max value, and setting the step value to
0.1, 0.01, etc- and it didn't make a difference.
I'll grab a copy of 1.6rc6 when it comes and see if that does it.
Cheers,
Mike
On Jan 29, 3:25 pm, "Richard D. Worth" wrote:
> I believe this may be related to
I believe this may be related to an issue fixed in the trunk. You should be
able to test in 1.6rc6, which will be out today. If that doesn't fix it, you
may want to try either increasing your max by say a factor of 10 (depending
on how wide your slider is) or decreasing step from 1 (the default) to
5 matches
Mail list logo
