Array literals and script only stack initialization (was Re: Developing first on android)

Bob Sneidar bobsneidar at iotecdigital.com
Tue Aug 22 11:21:24 EDT 2017


Here's the problem. Any project with a datagrid is going to tear through those ID's in a heartbeat as you are testing. 

Bob S


> On Aug 21, 2017, at 21:58 , Brian Milby via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> I think there may be a strategy to avoid a large part of the ID collision issue.    Wouldn't need full on UUIDs, just assign a range to each developer working the UI.    Upon import they could even be collapsed down to the natural order range or left as is.    It would require the temporary setting of the stack ID and being able to revert (thinking the alt ID may be useful here).    Dev A could start at 5001, Dev B at 6001, etc.    Main stack would remain with the 1001 series.    The idea would be that in the preopenstack handler that a check would be made for the dev environment and the developer.    The alt ID would be set for the stack.    When new objects are created, the engine would use the alt ID if set.    There would be a corresponding call to clear the stack alt ID to go back to the normal series (say for the primary developer) and probably also go in the close stack handler.    Custom properties could be used to track where each developer was in their sequence.





More information about the Use-livecode mailing list