4 Jun 2008 1:05 AM #101
I've made some fix for "multiple checked values". Can somebody test it please?
4 Jun 2008 5:28 AM #102
Yes I'm not saying that this snippet is up to the standard of the rest of your code, or that it will work for anyone else apart from me... but it might steer someone else in the right direction.
I don't know about typing partial words in, to be honest I never use this. A combo box that doesn't falsely select entries is more useful to me than one that allows autocomplete.
Once again thanks for sharing your code, it's made my project work a lot better
4 Jun 2008 5:33 AM #103
could you please test the current version of LovCombo if the issue is fixed? I've sacrificed partially typed texts for non-doubling entries.
Let me please know if it works now.
4 Jun 2008 5:36 AM #104
I can test it in around 12 hours (away from that machine at the moment). I'll test it and get back to you then.
4 Jun 2008 5:39 AM #105
4 Jun 2008 10:00 AM #106
4 Jun 2008 11:01 AM #107
To tell truth, I'm quite lame when IE is concerned. Does normal combo behave same if you configure it with onSelect:Ext.emptyFn?
4 Jun 2008 5:07 PM #108
Yes, the multiple values bug is now fixed. When I select "Door end panel" with your old code, it will then select "Door" as well. The new code only selects "Door end panel" which is the correct behaviour.
There are other issues with my implementation though (LovCombo doesn't automatically tick items in the list when bound to a record in a gridPanel), which are 'fixed' in the code I posted.
4 Jun 2008 9:33 PM #109
// display full list this.doQuery(this.allQuery);
4 Jun 2008 11:09 PM #110