Most common scenario: you switched to using a bold font, but didn't embed the bold font, just the normal font.
Second: The font didn't get embedded. Use -keep-generated-actionscript or -link-report to see if the font is really there Third: If fonts are in modules, make sure they are loaded and didn't get unloaded Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of djhatrick Sent: Monday, August 31, 2009 9:59 AM To: [email protected] Subject: [flexcoders] Re: Modules and fonts vanishing is giving me the cramps All of a sudden this happened again, to my modules, all my fonts are missing? I don't know how to restore my previous changes and see what simple change could have caused this. Other than replacing about 5 hours work and trying to re-add each change one at a time. On a scale of 1-10 for annoying problems this off the chart. I am not doing anything unusual here. I just made a few changes to some properties and collections and now I don't see any fonts. Any suggestions here? Thanks, Patrick --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, Alex Harui <aha...@...> wrote: > > Not sure I understood the problem, but the first thing to know about > sub-modules is that by default they load into sibling applicationdomains. > This is due to the way applicationdomains work. You can look at the diagrams > in the modules presentation on my blog to help visualize it. > > The main Flex app almost always has ModuleManager in it to support CSS and > Resource Modules. When you load a module, the main app's appDom is the parent > and the module gets loaded as a child of that appdom. That's what we want, > right? But the problem is that when that module tries to load a sub-module, > it is going to use the main apps' ModuleManager and thus the sub-module loads > as a child of the main app's appdom and not the module's appdom and then > sub-module can't see the module's classes. I'm guessing that's your problem. > > The solution is to explicitly set the applicationDomain parameter when > loading the sub-module. But even that can be tricky because when you say "new > ApplicationDomain(ApplicationDomain.currentDomain)" if that code is in a > class loaded in the main app's appdom, currentDomain is the main app's > appdom. So be sure the code that calls load is in the module and nowhere else. > > Maybe that'll help. > > Alex Harui > Flex SDK Developer > Adobe Systems Inc.<http://www.adobe.com/> > Blog: http://blogs.adobe.com/aharui > > From: [email protected]<mailto:flexcoders%40yahoogroups.com> > [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On > Behalf Of djhatrick > Sent: Friday, August 07, 2009 10:13 AM > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Modules and fonts vanishing is giving me the cramps > > > > Alex (or/and others) > > Here's my issue, I have a module that loads another module, a sub module. I > am trying to access the loaded module, the problem is that first, if I add it > to my shared code file, doesn't it compiled into the shell? or just a > reference.... > > I can access methods on my module through it's public properties, but I have > to assign it as wildcard, "*"? Which works 90 percent of the time, but once > in a while the module's or it's properties come back as undefined. So, I > tried the shared code solution again, but then my fonts mysteriously vanish > out of my app. > > Help, I am gonna go smack my head with a hammer a few times, Thanks, > Patrick >
