violinista
06-21-2007, 05:10 PM
hello 2 all,
I noticed some very strange issues when working with two connected combos, and I am posting it here, to discuss-maybe somebody already got it.
here is part of code for first combo:
cmbCombo1.on("select", function(combo,record,index){
cmbCombo2.store.load({params:{testParam:record.id}});
});
This all works well, it loads data regulary on the second combo. Now I go back to first combo, put some OTHER data and type data in second combo. It now filters not only new data which he got from first combo, but all data which he got earlier in the first request! It seems that combo has some caching mechanism which acts combo data to reside in memory...
So, does anybody noticed this issue?
Is there any workaround for this?
10x
I noticed some very strange issues when working with two connected combos, and I am posting it here, to discuss-maybe somebody already got it.
here is part of code for first combo:
cmbCombo1.on("select", function(combo,record,index){
cmbCombo2.store.load({params:{testParam:record.id}});
});
This all works well, it loads data regulary on the second combo. Now I go back to first combo, put some OTHER data and type data in second combo. It now filters not only new data which he got from first combo, but all data which he got earlier in the first request! It seems that combo has some caching mechanism which acts combo data to reside in memory...
So, does anybody noticed this issue?
Is there any workaround for this?
10x