Im using a simple static variables in a class named AppVars for such "app
lifetime" stuff :)
eg
public final class AppVars
{
public static var CurrentUserPermissions:ArrayCollection;
... //more app static memory
}
and then using AppVars.CurrentUserPermissions in the application
On 28 Feb 2017, at 01:08, bilbosax
<[email protected]<mailto:[email protected]>> wrote:
I have some components that I need to instantiate where a user will use
dropdowns and sliders and textinputs to choose values that they need to
search. When the search begins, I want to destroy the components so that
they are garbage collected, but I want the values for the various inputs to
persist so that when I instantiate the component again, I can set it to it's
last values. What structure do you guys like to use most to do this? I was
considering Flex Globals, but I have heard there are more sound ways of
doing it. Could you give me your suggestions? (i do not want to store them
in a sqlite database)
Thanks
--
View this message in context:
http://apache-flex-users.2333346.n4.nabble.com/Persistent-Data-tp14735.html
Sent from the Apache Flex Users mailing list archive at
Nabble.com<http://Nabble.com>.
SAMO NASLOVNIKU! / ONLY FOR THE INTENDED RECIPIENT!
Opozorilo: Ta elektronska pošta vsebuje informacije, ki so lahko zaupne narave
in so namenjene samo naslovniku. Če je bilo zaradi napake v naslovu ali pri
prenosu sporočilo poslano drugam, prosimo, da o tem obvestite njegovega
avtorja. Če sporočilo ni bilo namenjeno vam, ne smete uporabljati, razkriti,
širiti, kopirati, tiskati ali kakorkoli uporabiti informacije v sporočilu.
Disclaimer: This e-mail contains proprietary information some or all of which
may be legally privileged. It is for the intended recipient only. If an
addressing or transmission error has misdirected this e-mail, please notify the
author by replying to this e-mail. If you are not the intended recipient you
must not use, disclose, distribute, copy, print, or rely on this e-mail.
