[flexcomponents] Can you still make internal classes?

[Andy McIntosh]

In beta 2, the DragManager.as file contained 2 classes: DragManager and DragProxy.  In the production release, DragProxy is in it's own .as file and lives in a dragClasses package.  What's the advantage of breaking it out into another .as file?  Exposing it so it can be extended?  Is it still possible to have internal classes?  In the source from Beta 2, the DragManager class in DragManager.as was declared as public and DragProxy wasn't declared public or private.  I'm trying to do something similar with the production release and it's complaining about "A file found in a source-path can not have more than one externally visible definition."  Declaring the internal class as private causes flex to complain, "The private attribute may be used only on class property definitions." The entire concept of multiple classes per .as file seemed really bizarre to me at first, but I sort of understand the appeal now. I don't *need* to have an internal class, but I thought I'd give it a shot to keep the file structure a bit tighter.   Andy                          Andy McIntosh: Senior Engineer [EMAIL PROTECTED] | 303.956.2123 | aim - ameui __._,_.___ SPONSORED LINKS Custom software development Database development software Embedded software development Offshore software development Software development Software development company YAHOO! GROUPS LINKS  Visit your group "flexcomponents" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___