The way things are set up right now, due to the nesting of containers (div or DisplayObjectContainer), you do get (0,0) at the top. It will usually be necessary to have nested containers for scrolling purposes if nothing else.
As I'm going through the code, I don't see that IChrome is actually being recognized!! It looks like Panel is special-casing it somehow, but right now Panel is very messed up for me due to changes I've made in my workspace, so I'm not really certain what is going on it with. ‹peter On 3/9/17, 2:34 PM, "yishayw" <yishayj...@hotmail.com> wrote: >I think it makes sense to start the coordinates axis below the titlebar. >In >ExtJS they have the concept of docked components such as toolbars and >titles. So I think you can do (I changed syntax to pseudo-mxml) > ><container layout="vbox"> > <Button text="10px below titlebar" margin="10 0 0 0"/> > <label text="I'm right below button because of vbox layout"/> > <label text="this is the titlebar which is placed at the top" >docked="top"/> ></container> > >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.2333347.n4.nabble.com/FlexJS-Panel-tp60285p >60307.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
