Setting the itemRenderer goes thru the same error checking as any other assignment statement so that why there is no special case error checking code for IFactory. There is special handling for IFactory. For the inline MXML assignment to itemRenderer the compiler generates a "new ClassFactory()" and assigns that to itemRenderer. It is easier to understand if you look at the generated AS code by adding "-keep" to the command.
Below are some methods that might help you understand what is happening: *See references to StandardDefs.isIFactory(). *See the TypeCompatibility.check() method in the MXML compiler. Hope that helps, -Darrell -Darrell On Fri, Dec 5, 2014 at 9:29 AM, Darrell Loverin <darrell.love...@gmail.com> wrote: > I'll have some time this weekend to look at this a bit. > > > -Darrell > > On Thu, Dec 4, 2014 at 3:29 AM, Héctor A <neverbi...@gmail.com> wrote: > >> Hello again Darrell, and sorry for bothering one more time, >> >> I've been browsing the MXMLC source looking for IFactory info, but I >> couldn't find what I need. How do I determine the type of class/interface >> expected by an IFactory? is it posible or must I add it case by case? I've >> seen that when the type value is defined as a child tag it allows for other >> IFactory types as expected: >> >> <s:List> >> <s:itemRenderer> >> <custom:CustomFactory/> >> </s:itemRenderer> >> </s:List> >> >> However, when defining it as an attribute it allows for clases >> implementing IItemRenderer as well: >> >> <s:List itemRenderer="CustomRenderer"/> >> >> Is it possible to get the correct type dynamically? I haven't find >> anything on either the SDK or compiler source, so it may not be possible >> and implemented in the IDE itself. >> >> Best regards, >> >> >> On Tue, Nov 25, 2014 at 3:47 AM, Darrell Loverin < >> darrell.love...@gmail.com> wrote: >> >>> >>Right now none because the property is private, and if it wasn't, >>> just subclasses. >>> That sounds right to me. >>> >>> >>> -Darrell >>> >>> On Sun, Nov 23, 2014 at 8:34 PM, Héctor A <neverbi...@gmail.com> wrote: >>> >>>> >>>> >>property of type NavigationStack, marked with [ExcludeClass], what >>>>> does that mean? >>>>> >>>>> [ExcludeClass] prevents FlashBuilder from hinting the class and >>>>> excludes it from ASDoc. >>>>> >>>>> I know, I guess I made myself not too clear. I meant with regards to >>>> children nodes auto-completion, subclasses may not be excluded, but again, >>>> the default property is marked private, and at least in fd case the >>>> property info is not always available. So, which class types could appear >>>> in that case? None? NavigationStack subclasses? Right now none because >>>> the property is private, and if it wasn't, just subclasses. >>>> >>> >>> >> >
