My 0.02 is that export should mirror what the engine saves to the stack file such that import could exactly recreate an object (with some logic on how to handle ID collisions - overwrite, throw error, assign new ID...) On Sun, Feb 25, 2018 at 9:21 PM Monte Goulding via use-livecode < use-livecode@lists.runrev.com> wrote:
> > > > On 26 Feb 2018, at 9:45 am, Ali Lloyd via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > >> No there isn't, because if you aren't using it to completely import an > > object (i.e. set the properties of obj1 to the properties of obj2) it's > > your lookout what properties you include in the array to set - so just > > don't include all the forms of text. > > I must have misunderstood. I thought you were proposing adding all > gettable properties to the properties and not changing the way set works > (i.e. iterating all elements and setting them one at a time). > > Cheers > > Monte > _______________________________________________ > 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 > _______________________________________________ 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
