Some Basic Misunderstandings/Problems with RunRev - aka Help!

[David Burgun]

>You have two options:
>
>1) Create a standalone that is a splash screen only, that then opens 
>a separate stack residing in a folder (e.g. next to the app).  You 
>*can* then save your stack because it is not part of the standalone.
>
>2) I went through some of the same issues you are going through when 
>deciding whether to make my preferences stack (which has 8 tabs, and 
>dozens of control on each tab) a stack or a preferences file.  After 
>thinking about it for awhile I realized that if I used the stack 
>model, and then needed to change the format of the stack, e.g. add 
>another tab, or move some controls around, it was going to be 
>impossible to do so.  How, I wondered, was I going to get the data 
>out of the user's current preferences stack, and into the new 
>preferences stack?  In fact the more I thought about it, the more I 
>realized I would have to create an intermediate text file 
>representation to do any upgrade, and if I was going to do have to 
>do that, why not bite the bullet and just use the preferences file 
>from the start.
>
>So that's what I did.  It took a little more work to get things 
>working, but I am very glad I'm using a preferences file at this 
>point, rather than saving the data in the stack.

I don't really have that problem. If the "Preferences" Stack changes, 
then I can just throw away the old stack, I don't need the current 
settings to be saved acorss subsesqent versions of the Standalone App.

If I did need that (or need it in the future), then I could implement 
the text file solution just for the Prefs window. All the other 
Windows/Stacks can be saved as a normal RR stack. There are so many 
windows/stacks/controls that to save them all in as a text file would 
be unweildy I think.

Anyway, thanks for your help
Dave