UNIQUE CARD IDs

[Bill Vlahos]

Joe,

Could you change the name of the new duplicated card and then delete all the cards with the duplicate name?

For example the original cards are names Form1, Form2, etc.

When you duplicate the Form1 card call the duplicate DupForm1, etc.

When you are all done simply loop through the cards and delete any that contain "Dup".

Bill Vlahos
_________________
InfoWallet (http://www.infowallet.com) is about keeping your important life information with you, accessible, and secure.

On Aug 4, 2011, at 1:34 PM, Joe Lewis Wilkins wrote:

> Bob, Jacque,
> 
> Thanks. Perhaps you might like to know how I plan to use IDs in my application.
> 
> One of the Modules (stacks) has 56 basic forms. I record the ID of those forms in a field on the first card of that Module.
> 
> Subsequently, circumstances on one or more of the other Modules requires that one or more of these "basic" forms be duplicated, sometimes a number of times; particularly while I'm testing things, I need to revert back to the original stack with its 56 basic forms. Substituting a copy of that Module for the one that has been modified doesn't work. LC always brings up the modified stack - regardless of what I may do; I can tediously go through and delete the newly created cards, but that soon gets too much for even my patience level. 
> 
> Now I will just cycle through the cards and delete those whose ID differs from the ones whose IDs I've stored in the field. I'm sure I'll find other uses for this technique at some other point. I just wanted to be 100% sure that I wasn't creating a FrankenCode monster. (smile) I had considered using a system of marked cards to achieve the same result, but I'm already using that to track the Forms that I'll want to print in the final reports and I confuse easily. (smile)
> 
> Thanks again,
> 
> Joe Wilkins
> 
> On Aug 4, 2011, at 12:52 PM, J. Landman Gay wrote:
> 
>> On 8/4/11 1:51 PM, Joe Lewis Wilkins wrote:
>>> Hi Jaqui,
>>> 
>>> When new cards are created with the clone command, how sure can we be
>>> that the new card will be given a unique ID for the current stack?
>> 
>> 100% sure. As Bob said, no two objects can ever have the same ID.
>> 
>> -- 
>> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
>> HyperActive Software           |     http://www.hyperactivesw.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