On 5/2/17, 5:54 AM, "Peter Ent" wrote:
>Plus, there is no provision in the base layout for watching for new
>children or removed children. In the PAYG world, those feature would be
>part of other layouts:
>
>HorizontalLayoutWatchForAddChild
>HorizontalLayoutWatchForRemoveChild
>HorizontalLayoutW
I'm trying to find the balance between PAYG and mimicking the HTML/JS/CSS
side on the SWF side.
Take HorizontalLayout for example. On the JS side, this layout waits for
"childrenAdded" and then changes each child's display style to
"inline-block". If you then programmatically change one child's wi
-development.247.n4.nabble.com/FlexJS-Layout-Issue-Change-tp61440p61459.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Without having looked at every layout, it does make sense to me that
LayoutBase should not need to watch children for size changes on the JS
side. That's because the browser already has installed those listeners
and will re-calculate the layout as needed. The SWF-side will continue to
need to wat
The current listeners in LayoutBase (Basic Project) are for the children
of a component. Right now, if you have a Group with 10 buttons and
VerticalLayout, and you resize one of those buttons,
LayoutBase/VerticalLayout will detect that and automatically re-run the
VerticalLayout algorithm.
What I
il.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-Issue-Change-tp61440p61442.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi,
My main goal of the recent set of changes to containers and layouts was to make
the HTML/CSS/JS side as minimal as possible, letting the browser and friends
take care of things as much as possible. For the most part, I think it works.
But there is an issue that has been bothering me.
Righ
