Richard. So the id of a new object is indexed from the current stack ID. I thought (for no reason at all) it was the other way around, that the stack took on the id of a new object. I guess this way is more compact; the stack id property is the id counter.
Anyway, I will just do what I always did, never think about setting an id, and the issue (feature?) goes away. I use altID's, and they can continue to do their thing. Craig In a message dated 1/13/11 12:50:47 PM, ambassa...@fourthworld.com writes: > This is reasonable to expect given the stack's unique role as the > arbiter of IDs: as long as there's no internal list of all IDs > currently in use (and given the compact size of stack files I certainly > don't mind that there isn't), if you could set the stack ID lower you > would risk creating a new object whose ID would conflict with an > existing one. > _______________________________________________ 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
