make the dtaprovider as [bindable]
[Bindable]public var xData:XML; //as a property of the class
cbBox.dataProvider = xData;
and ofcoz nd do cbBox.invalidateList();
Hey thanks Sri
My dataProvider is Bindable already and the invalidateDisplayList(); didn't work either.
is your data an array or an arrayCollection?
May be after you get the xml from the server reassign the XML as the dataprovider... i dont think you have to do invalidateDisplayList() for this operation.. you have to do invalidateList() for any change in the data.
@SpaghettiCoder : its XML .. and i am using e4x to populate the CB
@Sri : There is only an invalidateDisplayList property of the CB not an invalidateList it shows a syntax error if I use that.
Also, tried reassigning the DP doesnt help.
after all this, i would just loop through the xml and populate in an ArrayCollection (Bindable). and make it dataprovider. and one more thing.. i would debug and see if the xml comming from the server is the same/different one .
Haha.. I think I am going to give the ArrayCollection idea a go..
Yes I debugged, the data coming back from the server is good and updated. The DataProvider has the new updated values, just the UI is not updating. Its frustrating.
no luck man.. doesnt work with the AC either...
If possible can you post your code here..??
If you could post some code,we probably would find a solution instead of trying to guess what is wrong.
Hey Sri and Adrian, thanks for the replies.
Found a link from the forums which talks of the EXACT problem that I am facing and it seems to be a bug in the Adobe SDK.
It has another link near the bottom of the thread. Have a look at that too. I am going to give 3.6 a try and see if this gets resolved.
Let me give it a shot with 3.6 else I'll paste the code here. Thanks again.
Ok, so it is indeed a bug with the Flex SDK 3.5. I downloaded SDK 3.6 and it worked like a charm, didnt have to do any refresh or anything, just had to assign the dataProviders.
Thanks Sri and Adrian for the help
I hope this post can help someone else who is stuck with the same issue. It was very hard to find any help with this issue. Its not documented well at all.
Oh... Thts nice 2 know...