We should probably build out some test cases for this. It looks like
PropertyWatcher.parentChanged should be called with the parent object goes
from null to non-null, but maybe that code doesn't exist.
-Alex
On 1/13/17, 10:03 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>Place where it blow up cause of these PropertyWatcher is in wrapUpdate
>(WatcherBase):
>
> try
>{
> wrappedFunction.apply(this);
>}
>catch(error:Error)
>{
>we are logging on console here error
>}
>
>Searching no-null object, but how and where ? If I do not have such code
>once this property get back from null to not null during work of
>application
>we won't notice it ?
>
>Piotr
>
>
>
>
>
>-----
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Problem-in-Fle
>xJSStore-tp58232p58239.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
