We have also expierenced the same problem, or similiar even.
After reading the docs on the opensource website
you will find that there is a flag you can set on the compiler arguments as follows:
by doing this, i think this allows the modules to work as before, inheriting the styles by default from the application.
There seems to be a new way of using the StyleManager in the current release of Flex 4.
Let me know if this helps.
The style manager did change in Flex4. In Flex3 there was only one style manager for all application and modules. Setting a style in one module would change the style for all modules. In Flex4 each application and module has its own style manager and can set styles independently. Setting -isolate-styles=false removes the style manager for an application/module so the Flex3 behavior can be maintained without needing to set the Flex3 compatibility version option. Compiling all applications and modules with -isolate-styles=false will give you a single style manager as in Flex3 but you will be prone to getting type coercion errors when using Spark components (that's one of the reasons we made the change).
From looking at the stack I don't recognize the problem. It would be helpful if you would write up a bug with a reproducible test case attached.
Thanks for this solution and tips!
I load Module from external server URL.
But how solve this problem without '-isolate-styles=false' ?
I have the same problem... trying with the compiler flag... The compiler flag works perfectly... If anyone is interested... i'll be happy to share the code... (redacted to a point of course)... but long story short, yes this flag works...