Thank you for your reply! Explicitly calling is something I didn't try. I thought of doing it, but it means tighter coupling and also implementation overhead in handling events etc. I thought if a child's invalidateDisplayList(), or at least invalidateSize has been called, the the parent container should automatically notice it and adjust accordingly, so I thought i miss something.
Is explicitly calling invalidateDisplayList() on the parent container a must, or is there a more flexible way doing this? --- In [email protected], "Manish Jethani" <[EMAIL PROTECTED]> wrote: > > Is the size of the UIComponent really changing? Is > invalidateDisplayList() getting called on the Canvas internally? If > not, try calling it explicitly and your Canvas should show scrollbars. > > On 4/21/07, vitcheff <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > I have following problem: > > > > Created a custom component by extending UIComponent using AS3. > > > > Added a Canvas to the Application container and then added an instance > > of that custom component. > > > > What the component does is load an image in a Loader instance and > > scales it down to fit into the canvas. However there is a slider that > > allows the image to be scaled back up and get larger than the canvas. > > At that moment I try to make the canvas scrollable without success. > > > > Canvas.clipContent is set to true; > > > > measure() is overridden in the component implementation to set > > measuredWidth and measuredheight to the width and height of the loaded > > image. > > > > invalidateSize() is also called when the image changes its size. > > > > Any help greatly appreciated! > > Thanks! > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > >
