Dan, Yes, this it what I was planning to do from my first email:
...when IE calls the <select>'s click handler, it does this *before* updating the .selectedIndex property, hence you cannot tell which item has been double-clicked on.
I could use a timer to get around this problem but it's a bit of a hack; does anybody have a better idea otherwise?
This is really the issue I'm working on I guess, the no click/dblclick event was what led me to it. Yes you're right it was a bad place to start off from. rob On 4/2/07, Dan G. Switzer, II <[EMAIL PROTECTED]> wrote:
Rob, >Because when you double-click on an option in one box it should transfer it >to the other box. >It's commonly used in applications hence I want to replicate a behaviour >that people will have seen and might expect - I would expect it in this >situation. The reason I ask, is just attach the click/dblclick to the select element--not the individual option elements. You not only attach less events (and avoid potential memory issues by moving the option elements around) but the select element will support the click/dblclick w/no problems. It's really easy to figure out which item is currently selected. -Dan
-- Rob Desbois Eml: [EMAIL PROTECTED] Tel: 01452 760631 Mob: 07946 705987 "There's a whale there's a whale there's a whale fish" he cried, and the whale was in full view. ...Then ooh welcome. Ahhh. Ooh mug welcome.
