LiveCode Forums.

I have a field containing data.

I want to retain the data while re-using a function
which will destroy it.

I then want the data to be available
in a field with the same name as the
original

Have looked at a couple of possibilities
but can't find anything that will suit.

I can, of course, copy the data and bring it
back easily enough but would like to know if
there is a more "elegant" solution available.

Reckon that if I learn something new every day
for a year I'll be an expert.

After further investigation I have found that "Clone"
will do the job very nicely.

What put me off was that the clone has the same
name as the original. Since that's what "Clone" does
I expected that the developer had realized this
and made appropriate arrangements but couldn't
get any clues from the documentation.

So I made a card to test.

Renaming isn't necessary: any commands apply
to the original not the clone.

Having cloned the field I wait until the procedure has
deleted its contents then delete the field. This gets
rid of the empty (original) and leaves the (full) clone
to do its job.

As the clone is offset from the original I'll move it back to
the position occupied by the original (even though it's not
visible) so that it won't be miles off the card if I ever need
to see it.

Neat.

Sounds like a job for a custom property.