I see where you are going here. So placing a group on a card has the effect of actually copying the group to the new card? That is the only way I can see it having new IDs if visited. I was under the impression that placing a group on another card simply made it visible, but I can see that would only work if backgroundBehavior was set to true. Faced with this twist, I don't think I would ever attempt to catalog and store every object on a card or in a stack. Too convoluted. (Or should I say Revoluted...?)
Bob S > On Oct 11, 2018, at 14:58 , Brian Milby via use-livecode > <use-livecode@lists.runrev.com> wrote: > > That works to touch the object, but I am recording a long ID and long name in > the exported script comment header. For background groups I didn’t want the > card in there since the group could be on multiple. If I left it in, then the > reported long ID would change depending on the last card containing the group > that was visited. So I adjust the value to be consistent. I also swap out the > stack path and use the name. > > Thanks, > Brian _______________________________________________ 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/listinfo/use-livecode
