Uniquly identifying a stack

[Peter Haworth]

Thanks Igor and Bill for the input.  Bill - t's almost like you read my
mind :-)

I think I may not have been clear enough in stating the problem.  The issue
is not the stack file name, it's the names of the stacks within the stack
file and what happens if they change.  But I think I have come up with a
solution to the problem which I'm in the process of implementing today.

Pete
lcSQL Software <http://www.lcsql.com>



On Mon, Jul 2, 2012 at 7:12 AM, Bill Vlahos <bvlahos at mac.com> wrote:

> Pete,
>
> Since the OS won't let you have more than one file with the same name in a
> directory you will either have different file names and/or different file
> paths even if the files have the same name. Internally you could keep track
> of the complete paths but since that is probably cumbersome for the user
> you could just ask the user to enter a label for stack.
>
> Bill Vlahos
> _________________
> InfoWallet (http://www.infowallet.com) is about keeping your important
> life information with you, accessible, and secure.
> lcTaskList: (http://www.infowallet.com/lctasklist/index.htm)
>
> On Jul 1, 2012, at 6:54 PM, Peter Haworth wrote:
>
> > You're probably right on the low frequency of stack name changes.  The
> idea
> > I had was similar to your recommendation of a GUID scheme in a custom
> > property, but maybe I'll just wait and see how much of a problem it turns
> > out to be.
> > Pete
> > lcSQL Software <http://www.lcsql.com>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>