[
https://issues.apache.org/jira/browse/FLEX-33998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849377#comment-13849377
]
Maurice Amsellem commented on FLEX-33998:
-----------------------------------------
> but how do you resolve conflicts with setting that and the properties
> individually?
Good point. I guess if setting the other properties individually, the result
will be unpredictable.
It's supposed to be a "convenience" property, so documentation should state
that it should be be used in combination with individual props.
> Also, if you do add this, please add a comment that overuse of these two
> properties is the #1 performance killer.
This property, or visible and includeInLayout properties in general?
What is the alternative ? states ?
> 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)
