Uniquly identifying a stack

[Peter Haworth]

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>



On Sun, Jul 1, 2012 at 6:22 PM, Richard Gaskin
<ambassador at fourthworld.com>wrote:

> 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 "MyStack".
>>
>> I have some ideas as to how to deal with this but wanted to check if
>> anyone
>> had come up with a generic solution to this problem.
>>
>
> In practice, stack names don't change frequently.  People come to rely on
> them as unique identifiers, and since the stack name isn't bound to the
> visible label there's no real need to, and doing so usually just requires
> otherwise-unnecessary code chages.
>
> Just the same, for those who might change their stack names one option may
> be to use a custom property with a carefully-design GUID scheme.
>
> --
>  Richard Gaskin
>  Fourth World
>  LiveCode training and consulting: http://www.fourthworld.com
>  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
>  Follow me on Twitter:  http://twitter.com/**FourthWorldSys<http://twitter.com/FourthWorldSys>
>
> ______________________________**_________________
> 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<http://lists.runrev.com/mailman/listinfo/use-livecode>
>