couple of win standalone questions.

[keyless]

I'm thinking of read/writing to a text file in order to give my program save ability (only will have to save a list of URLs). I know the troubles with user rights and Program Files folder in Vista, so I was thinking of creating and writing to the file in Application Data, in My Documents folder (I know I'll have to get the special path). Just wondering if this is the best place, or is there another more prefered location?


My second question has to do with the Splash Screen executable with another Stack, method of saving. I was hoping to use this method on a standalone that will have a lot more data to save, but not enough to warrent a DB.

I was wondering how I can prevent someone from just taking the stack and using it in Rev, or creating their own standalone from it.

[Mark]

I'm thinking of read/writing to a text file in order to give my program save ability (only will have to save a list of URLs). I know the troubles with user rights and Program Files folder in Vista, so I was thinking of creating and writing to the file in Application Data, in My Documents folder (I know I'll have to get the special path). Just wondering if this is the best place, or is there another more prefered location?

The easiest and most reliable solution is probably to create a special folder inside the user's documents folder and save your files there.

My second question has to do with the Splash Screen executable with another Stack, method of saving. I was hoping to use this method on a standalone that will have a lot more data to save, but not enough to warrent a DB.

This is possible, but note that your stack cant reside in the applications folder.

I was wondering how I can prevent someone from just taking the stack and using it in Rev, or creating their own standalone from it.

There are several ways to do this. One possibility is to encrypt your stack. Read it into a variable as a binary file, decrypt it, then

go stack myVarContainingStack

When you're done working with the stack, save it on disk, read it as a binary file into a variable, encrypt the variable, and save the data in the original location. Don't forget to delete the temporary file. Naturally, it is to be recommened do use this method only with small stacks.

Best,

Mark

[BvG]

Stacks have a password property, which you can set to not allow changes to be made. However, it does not stop the stack from working, but is a mild protection measure against simply reading all the scripts. Commercial add ons for the rev-ide from 3rd parties are protected this way.