Re: Uniquly identifying a stack

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 w

Re: Uniquly identifying a stack

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

Re: Uniquly identifying a stack

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 On Sun, Jul 1, 2012 at

Re: Uniquly identifying a stack

Hello, Peter, On 02/07/2012, at 11:02 AM, Peter Haworth wrote: > Probelm is I need to maintain uniqueness acorss two versions of the same > stack file. For example if both versions have a stack named "myStack" but > then its name gets changed to "YourStack" in one of the versions, it's no > long

Re: Uniquly identifying a stack

Peter Haworth wrote: Hi Richard, Probelm is I need to maintain uniqueness acorss two versions of the same stack file. For example if both versions have a stack named "myStack" but then its name gets changed to "YourStack" in one of the versions, it's no longer identifiable as the same stack as "

Re: Uniquly identifying a stack

Hi Richard, Probelm is I need to maintain uniqueness acorss two versions of the same stack file. For example if both versions have a stack named "myStack" but then its name gets changed to "YourStack" in one of the versions, it's no longer identifiable as the same stack as "MyStack". I have some

Re: Uniquly identifying a stack

Peter Haworth wrote: I know this has been discussed before but has anyone come up with a foolproof way to identify a stack? Stack IDs are an anomaly in the otherwise-consist use of IDs throughout LiveCode. Unlike other objects, the stack ID is merely a placeholder for the next available ID f

Uniquly identifying a stack

I know this has been discussed before but has anyone come up with a foolproof way to identify a stack? The ID doesn't work since it changes everytime a card or control is added to the stack. The name doesn't work because it too can change on a whim. Is anyone using the altID property for this pu