Flex 3 certainly behaves differently. If you take this example:
<s:BorderContainer width="100%" height="100%">
<s:Group top="0" right="20" bottom="0" left="0">
<s:Rect top="0" right="0" bottom="0" left="0" >
<s:stroke>
<s:SolidColorStroke color="red" weight="2" />
</s:stroke>
</s:Rect>
</s:Group>
<s:Spacer width="800" />
</s:BorderContainer>
and just replace BorderContainer with Canvas, leaving everything else as is,
the result will be different (the red line at the right side will be visible
inside the Canvas container which I consider "correct" and invisible in the
BorderContainer example which I consider "broken").
Furthermore, there is no easy fix for the Spark example. Setting minWidth on
BorderContainer has no effect, I guess one would need to create a new
BorderContainer skin and set the minWidth on the group that is added in the
chreateChildren() method or something like that. (Without trying, I am not
even sure what exactly would work for the BorderContainer example and I
would say I now quite understand what the layout classes do internally...)
Ok, but this is how it is, I just wanted to bring this up because it
surprised me and I would say I am a pretty seasoned Flex developer. I
probably just never used a skin that doesn't constrain its children. This
Spark thing, it has so many twists and turns :)
B.
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/Spark-and-percent-width-unexpected-behavior-tp33190p33258.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
