Hi Tracy, that is when I assign the values - when the Save Prefs button is
clicked. However, when the app quits, Flex autoflushes again, and the user
might have changed some of the params but does not want them as "Prefs". It
seems that this autoflush remembers where the values came from e.g.
soDrctrDash.data.ddParamsVO.vpID = drctrDashParamsVO.vpID;
soDrctrDash.data.ddParamsVO.rvpID = drctrDashParamsVO.rvpID;
soDrctrDash.data.ddParamsVO.divID = drctrDashParamsVO.divID;
and overwrites the saved user prefs with whatever the most recent values are. I
have never had this happen before and wonder if it is anything to do with
flash.net.registerClassAlias("soDrctrDash.DrctrDashParamsVO",
DrctrDashParamsVO);
soDrctrDash = SharedObject.getLocal("drctrDash");
TIA,
Mic.
--- In [email protected], "Tracy Spratt" <tr...@...> wrote:
>
> Don't assign values to the so until the user clicks the save prefs.
>
>
>
> Tracy Spratt,
>
> Lariat Services, development services available
>
> _____
>
> From: [email protected] [mailto:[email protected]] On
> Behalf Of chigwell23
> Sent: Wednesday, August 26, 2009 12:25 AM
> To: [email protected]
> Subject: [flexcoders] SharedObject - do I need to stop it flushing at app
> exit?
>
>
>
>
>
> Multiple dropdowns are used to configure stored procedure parameters to load
> a dashboard view. A "Save Preferences" button saves the current
> configuration to a local SO. The user can then change the parameters and
> load different dashboard views ..... problem is that when the app quits it
> autoflushes the latest parms and overwrites what the user saved. I looked
> for a way of stopping the autoflush at app quit but could not find one. TIA,
>
> Mic.
>
