Hi Alex, I've submitted this as a feature request on the Flex tracker. As an aside, the simplest solution is (I think) a very straightforward change to the Flex API. If the expected data fields were extended so that as well as 'icon' you passed in 'iconArguments' and those arguments, if present, were used as arguments to the asset constructor it would solve it all. And I don't think it would impact performance appreciably - the only difference is that internally Flex would call new SomeAssetClass(someArgs) instead of new SomeAssetClass(). The parameterisation of those constructors would open up so much more potential.
Cheers, Ian On 10/23/07, Alex Harui <[EMAIL PROTECTED]> wrote: > > If we can figure out a way to allow this in the future, we will. You > aren't the first person to ask for it. When we wrote 2.0, we were so > worried about performance we made assumptions that skipped levels of > indirection like the one you want. > > >
