piotrz wrote > Yes I know, but I've started to investigate why you need to dispatch any > events from VO class in order to have workable Binding.
This is how field binding to UI component has demonstrated in the example(s) that supplied within Apache FlexJS SDK. I followed that only; And I vaguely remember, the way of implementation only worked for me. If I remove the event dispatch on field's SET method, change do not reflect to the UI component that the field bind to (at least with my present nightly build 0.8.0 code that I updated some days back). -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Data-binding-fails-when-following-multiple-references-tp58022p58077.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
