Hi, yes. I did that component for our first migration, and I started removing it, but the problem was that was causing issues in the content layout, and even sometimes made changes that causes confusion to users, so I found the best solution was just to make it visible or not while maintain its place holder, so the content keep its layout intact.
But this is a good case to extend that code and swap for a custom bead that instead play with visibility make it disappear at all. Although maybe you could find that way the same issues I had. If you get a good behaviour, maybe would be good to add that extension variation to jewel. Thanks El dom., 31 may. 2020 a las 19:56, Andrew Wetmore (<[email protected]>) escribió: > are they visible = "false"? I think they still use their real estate when > invisible. Could you dynamically remove them from currentState when they > are not needed? I think I did that in past Flex apps. > > a > > On Sun, May 31, 2020 at 11:15 AM Piotr Zarzycki <[email protected] > > > wrote: > > > Hi Carlos, > > > > We are using Wizard in our application and I wanted to improve some > view. I > > have noticed that buttons previous/next - can be hidden, but still > taking > > place in the UI when they were hidden. > > > > I think it should be used display: none here [1] - Did you use visibility > > here for some reason? > > > > [1] > > > > > https://github.com/apache/royale-asjs/blob/2d23245729c7ec550661338a46188a34c267e848/frameworks/projects/Jewel/src/main/royale/org/apache/royale/jewel/beads/views/WizardView.as#L310 > > > > Thanks, > > -- > > > > Piotr Zarzycki > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > <https://www.patreon.com/piotrzarzycki>* > > > > > -- > Andrew Wetmore > > http://cottage14.blogspot.com/ > -- Carlos Rovira http://about.me/carlosrovira
