I have a theory it's the data bindings to the data property in the item renderer or the data provider in the list.
The data property of an item renderer can be null and so try catch blocks are placed around those assignments and then the errors are ignored. I can't recall if the try catch block is in the list, the item renderer or the data binding generated code. Maybe somewhere else. IIRC That's why in item renderers it's recommended to override the data setter and check for null rather than use bindings. A simple test should show if errors are being generated from that. Hopefully, Bilbos changes fixed it. On Dec 10, 2016 1:11 PM, "Nemi" <nemino...@gmail.com> wrote: > Did you find out what is making those many Errors? > > > > -- > View this message in context: http://apache-flex-users. > 2333346.n4.nabble.com/Scout-What-does-this-mean-tp14126p14317.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
