For the most part, I agree with what Muzak has to say. It appears that if you set an empty public setter function for the property with a private getter, no runtime error is thrown. I'm left wondering why the virtual machine needs to assign children of movieclips as instance named properties. In Flex, we use getChildByName(), and if we want to we assign a child to a property. I am working on a project at this very moment that demands complex integration between CS3 and Flex, and I have to say, it has not been easy coming up with a clean way to integrate these differences.
On 7/13/07, Muzak <[EMAIL PROTECTED]> wrote:
> Muzak - I share some of your frustrations though I see why they've done it. Then I'd like to hear 'why', because I can't think of anything. Declaring instances in the class is a must (IMO). As you said, you don't have to look at the fla to know what you're dealing with. Another important thing is that when declaring them as properties of the class, using strong typing, you'll get codehints. Assets that get automatically declared will give you no codehints at all. > Adjusting the publish settings and setting the instances to public > doesn't seem great. The instances *have* to be public and *will* be public, doesn't matter if you declare them yourself or if they're automatically declared. There's no way around it. Everything put on stage/timeline is public.. To make things worse, this feature can only be disabled on a document level, not globally. Edit > Preferences > ActionScript 3 Settings > *nada* It can only be disabled through the Publish Settings. So the more I look into this feature, the worse it gets.. Makes me wonder who they let into beta this time.. I've already made up my mind a while ago, I won't be doing any AS3 development with FCS3, I'll use the real thing: Flex. The only interesting thing about FCS3 for me is creating components to be used in Flex (using the Component Kit), which leads me to another annoying result because of the "stage-assets-will-be-public" feature: When creating an FCS3 component to be used in Flex, with assets on stage, those assets also become public in Flex and there's no way around it. <sigh /> regards, Muzak ----- Original Message ----- From: "Sunil Jolly" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, July 13, 2007 11:11 AM Subject: RE: [Flashcoders] Accessing MovieClips on a timeline from an AS3 class Muzak - I share some of your frustrations though I see why they've done it. So what do people think the best practice for this is? I don't like the idea of not declaring the MCs/Buttons in the class because it's a great help knowing what a class can deal with without having to refer to the Flash file constantly. Adjusting the publish settings and setting the instances to public doesn't seem great. Using getChildByName is a bit of a long solution too! Also how would FDT (when the AS3 version is finally released!!) handle this? Without declaring the instances they wouldn't have access to the Flash stage before compilation would they? So I guess you'll have to declare them for that functionality to work. Thanks, Sunil _______________________________________________ [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
