Well, it doesn't ring any bells, but someone else hit a problem where they were loading the module twice and timing issues from the module being cached in the browser cache affected whether it worked or not.
The classic no-show problem is when the IModuleInfo handle returned from ModuleManager is kept only in a local variable to the function that calls ModuleManager.getModule Then a GC can punt the module and that can happen "randomly". If you are using ModuleLoader, you won't run into this problem. How does the animation SWF work? Is it code-based, frame-based, timer-based? We pump up the frame-rate during app startup, so that could affect animations. I guess I would start by proving after no-show that the module actually exists, and introspect it for sizes, parenting, invalidation flags, etc. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ben.clinkinbeard Sent: Thursday, March 13, 2008 8:00 PM To: [email protected] Subject: [flexcoders] Re: Why are modules so buggy? Thanks Alex. Unfortunately, and as usually seems to be the case, this is happening inside of a fairly complex structure. Something else I just noticed though is also strange. When the app loads we have a SWF that gets loaded and plays an animation before presenting a button that can be clicked which takes you to the module. When the problem arises as I originally described, the intro animation also plays much quicker than usual. Its at least twice as fast as the SWF plays when the problem is not present. Does that give you any clues? Thanks, Ben --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > It is a known bug that % width/height doesn't work in modules and using > percentWidth/Height is the workaround. > > > > Can't think of any reason for the second behavior. I'll look at a test > case if you want. > > > > ________________________________ > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of ben.clinkinbeard > Sent: Thursday, March 13, 2008 7:04 AM > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Why are modules so buggy? > > > > I've admittedly only been using them for a short time but they seem > phenomenally fickle. Our basic setup is that we have States defined in > the main app, each of which holds a module and sets its visibility > accordingly. Couldn't be much more straightforward. > > The other day my module stopped appearing when I set the layout > property of one of its child components (TeaserWindow). The way I > ended up fixing it was by changing the mx:Module tag from width="100%" > height="100%" to percentWidth="100" percentHeight="100". > > Today my module has stopped showing up when I changed one of > TeaserWindow's child components (a Button) from being added to > rawChildren to being added as a regular child. TeaserWindow has 3 > child buttons and only this specific one being in children causes this > issue. The (totally illogical) "fix" of using percentWidth and > percentHeight is not preventing this latest absurd behavior. > > I am at a complete loss as to how the child composition of a child of > the Module or the layout mode of a child could cause the entire module > not to show. Note that even when it doesn't show it reports its > visible property as true and width and height as being correct. > > Am I taking crazy pills? >
