I don't know which classes end up in which swc, but the same rule may apply for Spark only projects in which case Spark classes extending mx ones may be a no no as well.
regards, Peter
On 9 June 2015 at 15:35, Alex Harui <aha...@adobe.com> wrote:
Peter is correct that you want to be careful about having mx-only classes depend on Spark classes. You could try making mx classes the base class for the Spark classes, so the Spark subclasses would add in the AdvancedStyleClient, but the guts of the work is all done in the mx base classes. -Alex
