Two mxml component share same as combobox

Question

Hi all,
     I write custom Combobox component. At the first mxml component call Main.mxml , I have added it. Such as:
---- Main.mxml component---
<mx:Canvas xmlns:mx="http://www.adobe.com/2006/mxml" width="100%" height="100%" xmlns:component="component.*" >
<mx:VBox>
     <component:AutoSuggest id="stock" dataProvider="{StaticDataCollection.stockArray}" autoCompleteSuggest="true"               styleName="
myComboBox" width="65" tabEnabled="true" tabIndex="1" change="upperLetter(event)"/>
</mx:VBox>
<mx:VBox
>
<component:TradingDiary id="tradingDiary" catalogueDetailList="{catalogTotalLst}" selectIndex="{catalogIndex}"/>
</mx:VBox>
     From above code, I also use TradingDiary component, and at this component, I also used combobox AutoSuggest component such as:
---- TradingDiary.mxml component---
<mx:Canvas xmlns:mx="http://www.adobe.com/2006/mxml" width="100%" height="100%" xmlns:component="component.*"> 
     ....<mx:VBox id="vbBelongStockName" width="155" paddingTop="5">
 <component:AutoSuggest id="stockCode" dataProvider="{StaticDataCollection.stockArray}" autoCompleteSuggest="true"styleName="
myComboBox" width="65" change="upperLetter(event)"/>
 </mx:VBox>
      And now, when I operate to this combobox, both combobox at Main.mxml and  TradingDiary.mxml have same action ? How I solve my problem.
     And now, when I operate to this combobox, both combobox at Main.mxml and  TradingDiary.mxml have same action ? How I solve my problem.

Answer 1

Hi quoc_thai,
I think since you are giving the same dataProvider StaticDataCollection.stockArray for both of your components and also you are calling the same function on change event ...change="upperLetter(event)". Are you applying the same logic in both the function in your two components...??
I think StaticDataCollection.stockArray gives you a reference to the static stockArray(Array) of your StaticDataCollection class. Since you are giving the same dataProvider to both of your components I suspect you are facing this problem.
Thanks,
Bhasker