Thanks to everyone who replied. I too had come across the ~ backup file
but as I had detected that this only happened when saving failed (due
to some scripting bug), I had not considered this corruption. However
it is good to have to in mind as my program can then check it's saves
and restore it's own stacks if required.
As regards the data stack, it won't have many cards, probably only
20-30 with each one holding a different type of data, rather than using
the rolodex metaphor. I think I would rather stay with the standard
stack for data storage as it is easier to manipulate & upgrade.
Given the comments so far, as well as my own thoughts, I think I will
go with the single stack file, with sub-stacks separated in the build.
Thanks again,
Sarah
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
- Stack file organisation Sarah
- Re: Stack file organisation Jan Schenkel
- Re: Stack file organisation Wolfgang M. Bereuter
- Re: Stack file organisation Sarah
- Re: Stack file organisation J. Landman Gay
- Re: Stack file organisation Ted
- Re: Stack file organisation Richard Gaskin
- Re: Stack file organisation Ted
- Re: Stack file organisation Richard Gaskin
