Some background just to give reasoning behind the insanity. Regarding First Frame, the point of bounding box on the first frame is to give the component initial widht and height values. If there is nothing on the first frame, you're width and height properties (a.k.a. you're __width and __height private properties of UIComponent) will be 0, thus when you go to position in your size function, you won't have any room.
Therefore, the bounding box gives your coponent a default value for width and heigth. That's why a List component is 100x100 when you drag it to the stage. The 2nd reason is because LivePreview needs a default width and height to draw. If there is nothing on frame 1, it doesn't know how big to be, thus the defautl size will be 0x0, and thus you're LivePreview will show nothing except for tiny blue outlines. You have to have SOMETHING on frame 1. mx.core.View hides boundingBox_mc for you, so the user will never see it. Regarding assets, that is only to ensure that your components assets (images & graphics) as well as the classes are exported into the SWF. If you are not creating them dynamically, and actually using them on frame 1, there is no reason for an assets layer & frame then. ----- Original Message ----- From: "Rich Rodecker" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" <[email protected]> Sent: Tuesday, March 07, 2006 1:15 PM Subject: Re: [Flashcoders] components within custom components yeah it just seemd really wierd to do that. if I have my components on the stage in the first frame, and all i'm doing is hiding or showing the components, do i still need to put all of the components on an asset layer? On 3/7/06, JesterXL <[EMAIL PROTECTED]> wrote: > Not sure what the heck the docs are talking about. I use the SWC's on > asset > layers all the time and it works great. > > To get a LivePreview to work, there are a number of factors, but the big > one > is ensuring a boundingBox is on frame 1 with a size bigger than 0x0, so > you > can actually see it. > > ----- Original Message ----- > From: "Rich Rodecker" <[EMAIL PROTECTED]> > To: "Flashcoders mailing list" <[email protected]> > Sent: Tuesday, March 07, 2006 12:53 PM > Subject: [Flashcoders] components within custom components > > > i posted this q on my blog, but wnated to ask here too: > > So, I'm taking my frist foray into building a legit flash component, > and it uses some standard v2 components. I read in the documentation > that you should use the component mc's instead of the compiled clips > for the v2 components, but I didn't see any reasoning as to why. I > made the switch, and I lost out on the live preview for components > withing my component. Can anyone shed some light for me? > _______________________________________________ > [email protected] > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com > > _______________________________________________ > [email protected] > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com > _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
