I have local changes that fixes Binding in Accordion by changing the lifecycle of the underlying Panel that AccordionItemRenderer subclasses. I'll push them before I shut down for the day. I want to try to fix the TitleBar height issue on JS first.
The reasoning is that ItemRenderers are supposed to have a different lifecycle. Normally, Binding is run as soon as the component is added as a child. But in renderers, Binding and layout isn't worth running at that point in the lifecycle because just about everything is dependent on the "data" property. So, the changes you'll see is that the AccordionItemRendererView overrides PanelView's completeSetup() and doesn't add the TitleBar or layout the renderer until data is set, which is after the model gets shared. FLEX-35320 is theoretically a feature request. The current Binding implementation doesn't support changing the "host", but a fancier, fatter and slower Binding implementation can. PAYG and all that. Thanks, -Alex On 6/5/17, 11:12 PM, "yishayw" <yishayj...@hotmail.com> wrote: >It's actually MXMLBeadViewDataBinding. The simplest solution may be to >avoid >using binding in TitleBarView and explicitly listen to TitleBar's >"modelChanged" event and TitleBarModel's "titleChange" event. But any >other >solution is fine by me. > > > >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FFlexJS-DataBinding-Problem-tp62073p6 >2133.html&data=02%7C01%7C%7Cb938b4dde0754478487808d4aca52e82%7Cfa7b1b5a7b3 >4438794aed2c178decee1%7C0%7C0%7C636323272830510197&sdata=iBHXLtdzCt6HDZbJZ >1eEaUL139K5F%2Bm7fEo9hAG5FbU%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.