Thanks Jorn. I did manage to figure it out, and actually redefined my needs so this trick was required.. :)
Your suggestion to use your plugin highlights where I have a problem with the jQuery autocomplete solutions though. I'm only meaning to highlight a problem I perceive here, not to bash anyone. I do appreciate all the work going on... The problem is that there are 3 or 4 potential autocomplete solutions on the plugin page. When examining the details they all seem to provide the same basic capabilities. So were then left with the date of the project to figure out which one is more current. Right now, Dylan's has a date of Sept 07 (jquery.org is not resolving for me right now, so I can't get much more accurate). Your plugin has a date of early 2007. The others seem to be 2006ish. So one is left to believe that Dylan's is more recent and (hopefully) more stable. But it's only through taking part in the lists and digging through lots of comments that we find out your plugin is the more recent. Throw into the mix that for myself, I'm writing an application - not a web site. So I am doing lookups against a database and need to display the found text, but store and use the related ID field. This is workable in both, but the documentation for this is lacking. So in terms of simply doing an autocomplete, yep a plugin exists - though choosing the "right" plugin can be a challenge. In terms of using an autocomplete in a similar fashion as a drop down list (display text, but use the value), this is even more of a challenge. My thoughts are that you and Dylan (and Dan) all seem to be collaborating, so why not make this more apparent on the various web pages and provide a link to the recommended plugin? Or better yet, maybe jQuery should create a "core" autocomplete? (that's a challenge I know because there are so many different needs/use cases out there). But in the meantime documentation needs to be improved. I've already had to dig through Dylan's plugin to find options that seemed "obvious" but were not in his documentation (his docs do say they are out of date though...) I do appreciate the massive effort you and many others put into the excellent plugins I use and thank everyone for their hard work. Hopefully this will help highlight a perception problem from the general public.. :) Shawn Jörn Zaefferer wrote: > > Shawn schrieb: >> I'm using the autocomplete plugin found at >> http://www.dyve.net/jquery/?autocomplete. >> >> I'm trying to set a second parameter to be passed to my serverside >> code, and am getting odd behavior. I'm stumped on this one. >> >> [...] >> >> Any tips how I do this?? Thanks in advance. >> > Try to specify a callback as the value (returning the value at the time > the request is prepared), using this successor of Dylan's plugin: > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > Until the 1.0 release is done (soon), you should give the latest > revision a try: > http://dev.jquery.com/view/trunk/plugins/autocomplete/jquery.autocomplete.js > > > Jörn
