Hi, El lun., 8 abr. 2019 a las 12:59, Kessler CTR Mark J (<[email protected]>) escribió:
> For the apps we create we use both cases. > > 1. Make something invisible, but not remove it's layout space. This > matches Carlos's example, by allowed a static sized interface even when > parts are not visible. > This for me should be a bead for modern Royale > > 2. Make something invisible and remove it's layout space. Standard > items, such as hiding interface / buttons / allowing things to collapse. > This is current visible that we have now on UIBase > > > We have used the "includeInLayout" and "visible" properties together > to replace the states (includeIn and excludeFrom) in some use cases where > we needed forms with fully created components on loading a popup. It was > the only way to get our validation manager to work properly. For us, Flex > states never really worked as intended for this scenario even when we tried > the "creationPolicy='all '". It introduced quarks for component > validation. But that doesn't seem to be a problem yet > > I'm ok with any method of doing these 2 (mean hidden and hidden without > layout), just as long as we can do both. > Right, I think we should have both, the most used baked in UIBase since the use is huge, the other be available in beads and use in the combination each edge case needs. > > > -Mark K > -- Carlos Rovira http://about.me/carlosrovira
