Dave, Have you tried compiling the css file into a separate .swf file and loading it at runtime in the application via StyleManager.loadStyleDeclarations()? This ensures all style definitions are available at runtime, not just the ones for components that are referenced in the application at compile time.
oliver --- In flexcoders@yahoogroups.com, "dave_defusion" <[EMAIL PROTECTED]> wrote: > > We have an application with each core section of the application being > a module (as some users will get access to a restricted set of the app > sections). > > We have all the CSS declared (via <mx:Style source="..." /> tags) in > the application MXML file. We then compile using a link report to > optimize each of the modules for our application and everything seems > to work fine. > > However now the application is nearly finished we just started to > really skin the application (we started with the OSX stylesheet from > scalenine and tweaked from there) everything looked ok until we > noticed some oddities. > > The things we noticed were that you could click on a textarea within a > module but you couldn't type into it and wherever date choosers are > used we got the OSX style chrome on the date chooser but couldn't see > nor choose any dates. Removing the OSX stylesheet fixed both of these > problems. > > I tried tweaking the OSX stylesheet but that did not resolve the > problem the only thing that I did which resolved all these strange > issues was to include the OSX stylesheet within each of the modules > themselves. > > I know I get a few warnings when compiling stating that certain CSS > declarations aren't going to be evaluated, but the fact that the > styles for things like the date chooser are in the app when the CSS is > only in the main application is really confusing. >
