Saving Changes in a Standalone

[Peter Haworth]

You're not doing anything wrong - Revolution does not allow data,  
custom props, etc to be saved in a standalone application.  I was just  
bitten by this a couple of weeks ago.  I'm using a database to store  
all my data so that wasn't an issue, but I also use custom props whose  
settings have to survive across runs of the application.  I ended up  
writing getProp and setProp handlers for the custom props I cared  
about to store them in an external preferences file.


Pete Haworth








On Jul 1, 2010, at 2:46 PM, use-revolution-request at lists.runrev.com  
wrote:

> Message: 24
> Date: Thu, 01 Jul 2010 17:43:48 -0400
> From: Gregory Lypny <gregory.lypny at videotron.ca>
> Subject: Saving Changes in a Standalone
> To: Revolution <use-revolution at lists.runrev.com>
> Message-ID: <D8DD99D7-D3FF-4A81-9968-BCC0ECFA7156 at videotron.ca>
> Content-Type: text/plain; charset=us-ascii
>
> Hi everyone,
>
> I suspect this has come up before.  I just built a standalone  
> version of a stack that allows users to import data into fields.   
> Custom props are set during a user's session and various other  
> changes occur.  I have the following save handler in the stack  
> script, but when I quit the standalone and reopen it, none of the  
> changes has been kept!
>
> on closeStack
> save this stack
> end closeStack
>
> What am I doing wrong?  I thought that the contents of fields,  
> changes to button menus, and custom props would be saved.
>
> Regards,
>
> Gregory