How to Reset ID's of Controls

Peter Haworth pete at
Mon Jan 27 14:57:06 EST 2014

Hi Richard,
I know that's why this capability was introduced but I've always wondered
if a vcs could get by without it.

The ID of a stack has always been changeable and, as I understand it,
indicates the ID of the next control to be created in the stack.  That
being the case, it seems like it would be possible for the vcs to sort a
stack's controls by their id number, create the stack, set the ID of the
stack to the id of the first control to be recreated, then recreate the
controls.  There could be gaps in the control ids of course, in which case,
the stack ID would have to be manipulated to bridge the gap.

I'm probably missing something obvious but wouldn't that work?.

lcSQL Software <>
Home of lcStackBrowser <> and
SQLiteAdmin <>

On Mon, Jan 27, 2014 at 10:43 AM, Richard Gaskin <ambassador at
> wrote:

> dunbarx wrote:
> > I was comforted back in the day with engine assigned ID's that were
> > not user settable. It was nice to know that these were unique and
> > somewhat apart from all other properties.
> >
> >
> > What was the rationale for making them changeable?
> It wouldn't be possible to make a text-based version control system
> without it, since such a system needs to reconstruct objects with complete
> fidelity.
> There's a warning in the Dictionary to avoid using them unless you have
> good reason to.  As long as we don't go out of our way to modify them this
> won't affect us at all.
> --
>  Richard Gaskin
>  Fourth World
>  LiveCode training and consulting:
>  Webzine for LiveCode developers:
>  Follow me on Twitter:
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list