On 8/5/11 1:27 AM, Joe Lewis Wilkins wrote:
Sean,
I considered that, since I have them set to cantDelete already, but I
was too concerned that in cloning them, they would retain that
property.
Cloned cards are identical in every respect except their ID, so the
cantDelete property should stay
Right after the cloning, set the cantDelete property to FALSE..
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listin
Sean,
I considered that, since I have them set to cantDelete already, but I was too
concerned that in cloning them, they would retain that property.
Thanks,
Joe Lewis Wilkins
Architect
On Aug 4, 2011, at 11:18 PM, Shao Sean wrote:
> You can always use the cantDelete property for the master f
Thanks Bill,
I have too many references and cross references to the names of the various
Basic Forms and they must continue to "work" even on the duplicated "copies" so
what you suggest would not work. It's a pretty complex application. Some think
I'm crazy to even attempt to solve the problems
You can always use the cantDelete property for the master form cards..
http://docs.runrev.com/Property/cantDelete
# only run this after setting the cantDelete property to TRUE on the
cards you want to keep
# every other card will be deleted, so exercise caution..
lock messages -- suppresse
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 a
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
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 |
Because if the engine did not make sure of it, things would get really, really
hosed in your stack in a hurry. The engine relies on the fact that every object
has it's own unique id, and so does not leave it up to us. Someone in a past
thread was trying to set the id of the stack so that he coul
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?
TIA,
Joe Lewis Wilkins
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visi
10 matches
Mail list logo