-
1. Re: Why don't data driven components have a dataProviderChange event?
drkstr_1 Aug 19, 2011 7:34 AM (in response to hidarikani)Because the dataProvider has one already... assuming it's a bindable ICollectionView that is, and if it's not than it's a non issue.
-
2. Re: Why don't data driven components have a dataProviderChange event?
saisri2k2 Aug 19, 2011 9:04 AM (in response to hidarikani)may be a changeWatcher on the dataprovider will help?
-
3. Re: Why don't data driven components have a dataProviderChange event?
Shongrunden Aug 20, 2011 12:56 AM (in response to hidarikani)Are you looking for dataProviderChanged?
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark">
<fx:Script>
<![CDATA[
public function handle(e:Event):void {
trace(e.type);
}
]]>
</fx:Script>
<s:layout>
<s:VerticalLayout />
</s:layout>
<s:Button label="change dataProvider" click="list.dataProvider = new ArrayList([1,2,3])" />
<s:List id="list" preinitialize="list.addEventListener('dataProviderChanged', handle)">
<s:dataProvider>
<s:ArrayList>
<s:source>
[0,1,2,3,4,5]
</s:source>
</s:ArrayList>
</s:dataProvider>
</s:List>
</s:Application>
-
4. Re: Why don't data driven components have a dataProviderChange event?
hidarikani Aug 21, 2011 11:35 PM (in response to Shongrunden) -
5. Re: Why don't data driven components have a dataProviderChange event?
hidarikani Sep 15, 2011 11:47 PM (in response to hidarikani)Is this a documentation bug or is this event a secret?
-
6. Re: Why don't data driven components have a dataProviderChange event?
oldMster Sep 16, 2011 9:28 AM (in response to hidarikani)Seems to be pretty well hidden in the documentation. It is referenced in text as an event on the DataProvider:IList property, but IList doesn't have any documented events except CollectionChange, so I'd call it a bug.
Mark
-
7. Re: Why don't data driven components have a dataProviderChange event?
Flex harUI Sep 16, 2011 10:03 AM (in response to oldMster)Many, but not all, properties in the Flex SDK dispatch a "propertyName +
Change" event.
If we listed them all under the Events section it would be hard to find the
more interesting events.
If we used the propertyChangeEvent, it would overwhelm the handlers.
Anyway, feel free to file a doc bug at bugs.adobe.com/jira. Maybe we can
find a way to mark properties as dispatching a change event.





