i need to get the index number, and also the value of that index when i click on it in a multislider. the example they show in the multislider help file takes 2 clicks before it starts working properly, the way my multislider is being used, it is constantly loading lists of data, therefore every time i change the data list to display in the multislider, it takes 2 clicks before it works properly, and this is very inefficient. is there a solution to this?

multislider-output-indexvalue

The technique in the help file works fine, but the first change is "eaten" because things aren't initialized. This is the help file example, with the only change being that the multislider values are set to 0. 

I assume you are prepending the list with "setlist" when you load the sliders (otherwise you wouldn't have that problem). If sending a 'hot' list isn't an option (outputting the list when you load the sliders), you can 'prime' the index abstraction when you set the sliders.

I assume you are prepending the list with "setlist" when you load the sliders (otherwise you wouldn't have that problem).  If sending a 'hot' list isn't an option (outputting the list when you load the sliders), you can 'prime' the index abstraction when you set the sliders.

chris: it works fine in some contexts, but not in mine. i am aware of whats happening and why its not working on the first click; it is because there is nothing to compare to yet. what i want to know is if there is some other solution that isnt comparing old and new values. like, for instance, the simplest solution ever that i have been wondering for literally years why it doesnt exist for some reason: an outlet that reports the index/value of the last clicked slider.

metamax: that works a bit closer to what i have, i will have to try tinkering with it to see if i can incorporate it in to my patch.

i very specifically need it to output the index/value of the slider on the first click, after it has been loaded with new data. i cant post the patch because it relies on an external and other things, but basically what is happening is im taking the data of regions of notes and then displaying certain values along the multisliders. when i click the multislider it then changes the data of the note that it is displaying. therefore, i cant be giving it a first little "push", because its still going to be outputting something like 0 for index, and 0. for value, which will alter the data on the first note.

chris: it works fine in some contexts, but not in mine. i am aware of whats happening and why its not working on the first click; it is because there is nothing to compare to yet. what i want to know is if there is some other solution that isnt comparing old and new values. like, for instance, the simplest solution ever that i have been wondering for literally years why it doesnt exist for some reason: an outlet that reports the index/value of the last clicked slider. 

metamax: that works a bit closer to what i have, i will have to try tinkering with it to see if i can incorporate it in to my patch. 

i very specifically need it to output the index/value of the slider on the first click, after it has been loaded with new data. i cant post the patch because it relies on an external and other things, but basically what is happening is im taking the data of regions of notes and then displaying certain values along the multisliders. when i click the multislider it then changes the data of the note that it is displaying. therefore, i cant be giving it a first little "push", because its still going to be outputting something like 0 for index, and 0. for value, which will alter the data on the first note.


ah, very good. this is a much neater version than i currently had literally just figured out and got working; i always feel like when i do that kind of open/close of a gate in situations like that, that im taking an inefficient shortcut or something when there is probably a simpler (or more concise) way. thanks.

Ah, from your initial problem statement, I didn't understand your constraints. Maybe this is closer to what you wanted. Instead of gating, I'm just seeding the zl.compare with the generated list.

multislider output index/value