I actually looked at this recently but for the complete opposite reason. I saw a problem recently with binding to an xml root (just a normal binding as the top level reference to the XML instance) for generated code. The compiler was trying to generate both the normal binding *and* the XML binding I think (it was the xml binding which was causing the problem). I only wanted the regular binding, so I coded around it, but made a note to come back and look at it later.
I never ever used XML bindings in Flex, and even now I would probably choose to avoid them (by preference) if I was doing something in Flex (or Royale). I assum support for that that uses mx.binding.XMLNotifier in Flex as well as XMLWatcher. And relies on something we do not yet have (because I think it is not well known) : http://www.docsultant.com/site2/articles/flex_internals.html#xmlNotify I have not looked into what it would take to emulate this. We might want to consider whether Serkan's case is typical and needs supporting, or whether it is best to address it as a workaround. On Sat, May 9, 2020 at 4:57 PM Alex Harui <[email protected]> wrote: > Mostly to Greg and Harbs, > > Have you guys seen watcher type "xml" in the DataBinding data when setting > up watchers for XML DataBinding? I'm trying to understand if you've seen > it work. The switch statement in DataBindingBase setupWatchers doesn't > have a case for it. That seems to be Serkan's problem in > https://github.com/apache/royale-asjs/issues/819 > > Thoughts? > -Alex > >
