>In other words, docked items override the container's layout and change
>the
>coordinates axis point of origin.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-tp60285p
>60307.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
and change the
coordinates axis point of origin.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-tp60285p60307.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 3/9/17, 8:49 AM, "Peter Ent" wrote:
>The idea of "chrome" is that these are components that do not count as
>regular children and have special locations within the component. The
>TitleBar and ControlBar are considered chrome because if you ask for the
>children of the
che Flex PMC
>piotrzarzyck...@gmail.com
>
>
>--
>If you reply to this email, your message will be added to the discussion
>below:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-
>tp60285p60286.html
>To start a new topic under Apac
ge will be added to the discussion
below:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-
tp60285p60286.html
To start a new topic under Apache Flex Development, email
ml-node+s247n1...@n4.nabble.com
To unsubscribe from Apache Flex Development, click here
<http://apache-flex-dev
Hi Peter,
Let's say that you reconstructed Panel using new Group container - How can
we use there Chrome ?
I would go with ChromedContainer.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS
Hi,
I'm trying to determine if "chrome" is a necessity as part of Container or if a
specialty "ChromedContainer" should be made (or if at all).
Panel is one component that uses chrome (the TitleBar and ControlBar implement
IChrome). Is Panel used a lot?
As an alternative, Panel can be
I filed a bug:
https://issues.apache.org/jira/browse/FLEX-35144
I think it has to do with binding and reflection changes. Maybe we didn't
merge them in correctly to refactor-sprite?
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-Broken