Confirming a thing about IDs

Geoff Canyon gcanyon at
Thu Oct 11 17:32:52 EDT 2018

I guess I should have said, "as unique as the standard 'long id' form of
identification" meaning that there is no circumstance where the long id
will resolve correctly, but <type> id <id> of stack "<stack name>" will
fail, or field id <id> of card id <id> of stack "<stack name>" will fail.

I understand that there is no such thing as a permanent id in LC.

On Thu, Oct 11, 2018 at 2:15 PM Mark Wieder via use-livecode <
use-livecode at> wrote:

> On 10/11/2018 12:11 PM, Geoff Canyon via use-livecode wrote:
> > And as far as I know, there will never be any other button with id 1003
> in
> > that stack. So
> >
> > button id 1003 of stack "untitled 1"
> >
> > is a unique and permanent id for that button, no matter what card, group,
> > or background it is in/on or not.
> >
> > Is this correct? (mind blown if it is)
> Not quite. Aside from cloning objects and the datagrid weirdness, as
> already mentioned, ids have been mutable for several years now. The only
> restrictions are that you can't have duplicate object ids in the same
> stack and that you can't decrease the id of a stack (it can only be
> increased).
> --
>   Mark Wieder
>   ahsoftware at
> _______________________________________________
> 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