On 2/1/17, 10:25 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>And what about to replace by default and to have a property >appendBeads=true/false (false default) >An advanced dev would make this true to allow beads to be appended instead >to remove all. And that "check" >is like they know how this works pros/cons. > >Other way could have a bead that called <js:Appender> and inside introduce >beads that we want to add (something like >the bead condition that was proposed some time ago) Maybe. The first question is really: how important is it to try to make MXML-based-on-MXML work better than it did in regular Flex? In theory, because MXML for FlexJS outputs a data structure instead of code, it should be possible for MXMLDataInterpreter to do something more intelligent. I'm actually surprised it didn't work for Yishay. Yishay, please file a JIRA with a test case and I will investigate more later. -Alex
