On 6/7/07, Michael Schmalle <[EMAIL PROTECTED]> wrote: > That is a solution as well but, Adobe needs to make anything that is > IFactory and public renderer property. > > Why go to the trouble of typing IFactory when you are not making that > interface available publicly through a navButtonRenderer() property.
What you're saying totally makes sense. (When is that public bug database coming up?) I guess how that property ended up being mx_internal is, "Hey, let's make it an IFactory, but I'm not sure it should be part of the public API, so let me make it mx_internal for now (for our internal use) and maybe if there's demand we'll make it public in a future release of Flex." There's no package-level access in AS3 (AFAIK) so the next best thing is to make it mx_internal. A lot of the mx_internal stuff in the framework is "we really wanted to make it private but we had to access it from this other class so we made it mx_internal".
