long id trap for the unwary

[Craig Newman]

Neville.

I know this thread has been broken into parts, but what exactly is your question?

I made two stacks, The first with a button on it, and this in its script:

on mouseup

put the long id of field 1 of card 1 of stack "untitled 3" into fieldID

put the long ID of the owner of fieldID into groupID

put the owner of groupID into ownerID

end mouseup


The second stack (untitled 3) has a field  that has been grouped.

You get, in the SE, three pieces of information in those three variables. What does this do for you?

Craig

> On Jun 28, 2022, at 9:38 PM, Neville Smythe via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> No crashes or errors, I just didn’t get back the data I expected.
> 
> Does it really have anything to do with message paths?
> 
> I just expected
> 
>    the long id of field1 of card 1
> 
> to do what it says, that is, to return a specifier to (the instance of) field 1 on card 1. At the time I was iterating through all substacks and controls in a stack and wanted a specifier which would work for substacks as well as objects so the long id was the natural choice.
> 
> I understand why the long id of a group has to contain a reference to the  current card or the first card containing the group, but in this case I am actually specifying the card reference I want, so it *could* return what I expected, it just doesn’t. Tough cheese. (Oops, I mentioned c…..)
> 
> 
> Neville
> 
> 
> 
> 
> _______________________________________________
> 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