My personal opinion is that this is a bit of a kludge. Stacks should have their own unique ID like any other object, and internal objects should have their own unique ID inside each stack. The ID should be read only. If users want their own ID system, the AltID was a perfect solution for that. The ID counter could have been implemented as some kind of read only property of the stack. But that is all water under the bridge now.
Bob On Jan 13, 2011, at 9:46 AM, Richard Gaskin wrote: > Apparently you can set the ID of a stack to a higher number than it currently > is, but attempting to set it to a lower number will generate an error stating > "invalid id (must be greater than current id)". > > 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
