Save in Standalone
Roger Guay
rogerguay at centurytel.net
Sat Nov 15 19:46:28 EST 2003
Thanks, Graham. Makes sense now that I think about it. By a "data
stack" you must mean a .rev stack, as a standalone data stack would
have the same problem??? And, since I can't expect my users will have
Revolution installed on their machine, I guess I'll have to use
external files to save to and pull from?
Thanks, Roger
> Message: 6
> Date: Sat, 15 Nov 2003 23:36:37 +0100
> From: Graham Samuel <graham.samuel at wanadoo.fr>
> Subject: Re: Save in Standalone
> To: RunRev Users List <use-revolution at lists.runrev.com>
> Message-ID: <5.2.1.1.0.20031115233038.00c4ef90 at pop.wanadoo.fr>
> Content-Type: text/plain; charset="us-ascii"; format=flowed
>
> On Sat, 15 Nov 2003 09:42:52 -0800, Roger Guay
> <rogerguay at centurytel.net>
> wrote:
>
>> What do I need to do to allow the user of my Standalone app to save
>> changes they make to a field? What I'm finding is that field content
>> is not saved in subsequent openings of my Standalone app. Not so for
>> the RunRev project, however. I also find that changes to custom
>> properties are not saved in the Standalone but are in the RunRev
>> project. What's this about? BTW, I did try the Save Stack command
>> but
>> to no avail.
>
> Roger - in a standalone, the file that was your mainstack (and its
> substacks) becomes read-only, since they are now an application
> program,
> and most OSs (not Mac Classic) frown on self-modifying programs. So
> although you can change stuff while the program is running in RAM,
> when you
> quit all your changes are lost.
>
> To get the effect you need, you must separate your data from your
> application. It can still be in a stack (or lots of stacks), but it
> can't
> be part of your main app. In effect these data stacks will be
> documents of
> your application and as such they can be modified and saved in the
> usual way.
>
> I'm sure others will chime in with more details.
>
> HTH
>
> Graham
>
More information about the use-livecode
mailing list