Problem when using asmSelect on multiple selects

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create two different selects with different options
2. call .asmSelect on them both seperately
3. Select the first option in the second select

What is the expected output? What do you see instead?
I expect to add the first option to the second select, but instead i get
the first option of the first select

What version of the product are you using? On what operating system?
latest i guess...

Please provide any additional information below.
I seem to have found a fix - the problem is both options gets named
"asm0Option1", so when selecting the wrong option is selected. In the code
that creates the id:

if(!$t.attr('id')) $t.attr('id', 'asm' + index + 'option' + n);

if we instead use the name of the original select as a base, it should be fine:

if (!$t.attr('id')) $t.attr('id', $original.attr("id") + index + 'option' +
n); 

Original issue reported on code.google.com by skovse...@gmail.com on 22 Apr 2009 at 8:56

[GoogleCodeExporter]

This was an issue fixed in 1.0.4 (December). Can you double check to make sure 
that
you are not using the older version?

Original comment by ryancram...@gmail.com on 4 Jun 2009 at 3:07

[GoogleCodeExporter]

I had experienced this problem also, using asmSelect-1.0.1. I've now found that 
asmSelect-1.0.4a-beta solves the issue by incrementing the 'index' value at 
line 61.

Original comment by christop...@gmail.com on 28 Aug 2009 at 12:32

[GoogleCodeExporter]

Thanks a bunch guys - unfortunately I have since changed jobs, so I do not have
access to the codebase anymore, but I just checked with a former coworker and 
he says
that upgrating to 1.0.4a beta has resolved the issure.

Original comment by skovse...@gmail.com on 28 Aug 2009 at 8:14

[GoogleCodeExporter]

Hey,
i got also vers.  1.0.4a beta and when i add 2 select multiple forms, then 
asmselect
just "design" the first one and the second one looks normal.

What can i do against that?

Thanks and regards

Original comment by haschten...@gulli.com on 4 Nov 2009 at 9:09

[GoogleCodeExporter]

just wanted to second what haschten has said

Original comment by Hudson.A...@gmail.com on 6 Mar 2010 at 5:41

[GoogleCodeExporter]

i have the same problem with 2 select, only the first works fine

Original comment by MFnetwo...@gmail.com on 16 Mar 2010 at 3:45

[GoogleCodeExporter]

The problem commenters 4, 5 and 6 are describing only occurs when the 
"sortable" attribute is used. 

Original comment by blameito...@gmail.com on 10 Sep 2010 at 3:47