[
https://issues.apache.org/jira/browse/FLEX-33998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849414#comment-13849414
]
Alex Harui commented on FLEX-33998:
-----------------------------------
Yes, the last two or three apps I helped performance tune because they were
complaining about startup time or delays when shifting views were largely
related to using visible and includeInLayout together. This caused every MXML
instance to be instantiated at startup or when creating a new view, instead of
just the ones need. In some apps, there were 3 times as many hidden things as
visible things.
I know it makes other stuff less easy to code, but that's the price you pay for
not deferring work to "just-in-time"
> visibleAndIncludeInLayout combined property would be helpful
> ------------------------------------------------------------
>
> Key: FLEX-33998
> URL: https://issues.apache.org/jira/browse/FLEX-33998
> Project: Apache Flex
> Issue Type: New Feature
> Components: MXML Components
> Affects Versions: Apache Flex 4.11.0
> Reporter: Maurice Amsellem
> Priority: Minor
>
> To show/hide a component inside a Group in MXML, you need to set both visible
> and includeInLayout properties, through bindings.
> It would be convenient (and probably faster) to have a combined
> visibleAndIncludeInLayout to set both properties at once.
> {code}
> <s:HGroup>
> <s:Button id="clearButton" visible="{model.canClear}"
> includeInLayout="{model.canClear}"/>
> </s:HGroup>
> {code}
> by:
> {code}
> <s:HGroup>
> <s:Button id="clearButton" visibleAndIncludeInLayout="{model.canClear}" />
> </s:HGroup>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
