I've found that if you have open windows created by an application you can't just remove the application from the display list and set it to null -- the windows will remain open. Also, any listeners that have been registered will continue to fire even though the application component is no longer in the display list.
If you are going to use the shell model then it seems to me that you'll have to make sure to close all open windows created by the application and unregister listeners prior to dereferencing the application when logging off. Paul --- In [email protected], "Brian Dunphy" <[EMAIL PROTECTED]> wrote: > > Could be just me, but if that does work it seems like kind of a > hack... I think most applications would use something similar to the > shell concept. It let's you have a lot of flexibility on what > operations to perform on login/logout, and it will work for > applications outside of the browser I'm guessing. > > Brian > > On 1/30/07, Tracy Spratt <[EMAIL PROTECTED]> wrote: > > > > > > What abour navigateToUrl, pointing to the app itself, using _self as the > > target? > > > > Just thinking, haven't tried it. > > > > Tracy > > > > ________________________________ > > > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On > > Behalf Of brent_trx > > Sent: Tuesday, January 30, 2007 10:37 AM > > To: [email protected] > > Subject: [flexcoders] Re: Full Application Reset? > > > > > > That sounds like exactly what I need to do. Thanks for the help! > > > > > Don't feel bad, this left me scratching my head when I encountered it > > > as well. I was used to just displaying a titlewindow for a login > > > screen, making it modal, and having the application blurred in the > > > background. > > > > > > My way of implementing an application reset was to have a "shell" app > > > that handled the instantiation of a login or my main application. When > > > the shell app first loads, it displays a Login application... after > > > login, the login app gets removed and the main application gets > > > created. Upon logout, vice versa. > > > > > > Hope this helps! > > > > > > Brian > > > > > > On 1/30/07, Oleg Filipchuk <justversus@> wrote: > > > > > > > > Why don't you just refresh the page where your application is > > embedded? > > > > > > > > On 30/01/07, Brent Dearth <brent.dearth@ > wrote: > > > > > > > > > > > > > > > This has got to be an obvious implementation, but it's left me > > scratching > > > > my head. Here's my scenario: > > > > > > > > > > When user performs a logout in an authenticated flex > > application, I would > > > > like to fully re-initialize the application back to it's initial > > load state > > > > (as if the SWF was being accessed anew). All children components > > are reset, > > > > or ideally destroyed and re-created. There are portions of this > > application > > > > that may contain sensitive data, and thus, I'm not willing to > > leave it to > > > > chance by manually calling custom initialization functions on each > > component > > > > / sub-component / etc. > > > > > > > > > > I've thought about recursively iterating through the Application's > > > > children, looking for these custom methods and executing them when > > > > encountered, but there has got to be a cleaner, simpler way that I am > > > > missing. I didn't see much on the mx.core.Application > > documentation that was > > > > relevant, beyond accessing children properties manually. > > > > > > > > > > Ideas? > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Oleg Filipchuk > > > > > > > > > -- > > > Brian Dunphy > > > > > > > > > > > > > > -- > Brian Dunphy >
