Peter, I just meant that if there is one child, there is a different code path and when setActualSize() is called on that one child, includeInlayout is not there.
I see no harm in putting an if() statement around the setActualSize() call on the single child. This would then allow for certain instances like I am running into that require me to save processing during an operation where I don't want the single child sized. I want the parent Container to size but not the child becasue the child is invisible. :) Peace, Mike On 12/3/06, Peter Hall <[EMAIL PROTECTED]> wrote:
I think that is how includeInLayout is supposed to work. My impression was that includeInLayout=false means that the container will resize and position it just as if includeInLayout=true, but it will not affect the other children in the container. For example, if you have 4 buttons in a VBox, and the 3rd one has includeInLayout=false then the first 3 buttons will be laid out normally, but the 4th will be positioned on top of the 3rd one, as if the 3rd button didn't exist. Peter On 12/2/06, Michael Schmalle <[EMAIL PROTECTED]> wrote: > > Hi, > > I just thought I might run this passed the flex engineers. > > I see in the code path in BoxLayout, that if there is one child of the > Container, you do not honor includeInLayout. > > I think I wasted an hour trying to figure out why my child was still > resizing after I set includeInLayout to false. > > I know this might not be an issue for most but, I can for see some > developers like myself wanting this property consistent across the board. > Can you tell me why you didn't for sake of consistency do this? > > I have created a framework that is a subclass of Container and basically > one of my components is a Window. Think of it this way, you put a real heavy > duty component in as child one say, just a Tree alone will kill a resize > effect. Not being able to set includeInLayout to false on the one child > kills me and I have to make a hack workaround. BTW, I set the visible to > false on the child but, keep the titleBar. > > Anyway, I just thought I would share this. > > Peace, Mike > > -- > Teoti Graphix > http://www.teotigraphix.com > > Blog - Flex2Components > http://www.flex2components.com > > You can find more by solving the problem then by 'asking the question'. >
-- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
