Another approach would be using framework such as Robotlegs where the view/control can be initialized via Mediator. I have used the container-agnostic approach for quite some time and already forgot about this weird behavior of Views.
Tangent -----Original Message----- From: Cristian Spiescu [mailto:[email protected]] Sent: Sunday, June 09, 2013 4:56 PM To: [email protected] Subject: Re: ViewNavigator: using view instance instead of view class Thanks for the tip! Regards, Cristian On Jun 9, 2013 7:24 PM, "Jonathan Campos" <[email protected]> wrote: > Most people just create a good method to set the values as soon as the > view is created. Just respond to the viewActivate method. Trust me > that is the easiest way :) > > > On Sat, Jun 8, 2013 at 5:51 PM, Cristian Spiescu < > [email protected] > > wrote: > > > Thanks! This was my impression as well; > > > > you can change the destruction policy so that it isn't destroyed > >> > > This is true, but I'd need the instance before passing it to the > > view navigator, so that I can populate some data, the "classic way" > > (not by passing the data through the "data" parameter). > > > > get into the guts of Flex > >> > > Yes; looks doable, by hacking the viewNavigator.navigationStack > > (visibility mx_internal). > > > > Best regards, > > Cristian. > > > > > > On 08.06.2013 21:03, Jonathan Campos wrote: > > > >> you can change the destruction policy so that it isn't destroyed. > >> And > you > >> could get into the guts of Flex and make this change. But I don't > believe > >> it is readily available. > >> > >> J > >> > >> > >> On Sat, Jun 8, 2013 at 6:11 AM, Cristian Spiescu < > >> [email protected] > >> > >>> wrote: > >>> Hello, > >>> > >>> In some cases, I would like to push to the stack an instance of a > >>> view that is already constructed. > >>> Is this possible? > >>> > >>> Thanks in advance! > >>> Cristian. > >>> > >>> > >> > >> > > > > > -- > Jonathan Campos >
