Cheers Dan,

i am looking forward to it. The workaround is fine for the moment,
just not as slick as it could be :)

Phil

PS: I have a couple of plugins which i would like to get some feedback
on but nowhere to host them. Is there a code review section for jQuery
somewhere ? Maybe you know.


On Apr 12, 12:39 pm, "Dan G. Switzer, II" <[EMAIL PROTECTED]>
wrote:
> Phil,
>
> >I use a local array of the following form
>
> >values = [['Philip-f','2356'],['martin-b','2341']]
>
> >whereas the second value is the id of the user. When i select multiple
> >users i want the ids to accumulate somewhere so i can pass them in my
> >form as selectedUserIds. It is easy to add the ids to an array with
> >the result function but what happens if somebody deletes a name in the
> >middle. The related id is hard to delete from the selectedIds array.
>
> >So i guess the only option would be to have a function connected to
> >the submission of the form which reads the string in the textarea and
> >finds out the ids and injects those as parameters in the form, right ?
> >That works but maybe there is a better way to achieve that.
>
> This is actually what the findValue() method was introduced to do. However,
> Jörn has implemented the multiple values to the findValue() method yet. So
> at the moment, if you're using the multiple select you'll have to do your
> own parsing to match up the values in the text field to match up to their
> internal ids.
>
> You can use it on singular values, but not multiple values yet. I'll see if
> I can help on that portion over the next few days. Quite frankly, the
> multiselect functionality will probably take a few revisions to get working
> correctly. It's a new behavior and one that's likely to generate lots of
> feedback.
>
> -Dan

Reply via email to