I was just answering the question asked :-) What I usually do (and what we generally do in the IDE) is get a target object's long ID, put it in a variable and use that for subsequent references. That way you only pay the (again, very small) performance penalty once per usage. Obviously YMMV, I would never blanket-recommend ANY optimisation strategy as these things are almost always specific to the use case.
On Tue, 2 Feb 2016 at 18:21, Mark Waddingham <m...@livecode.com> wrote: > On 2016-02-02 19:00, Mark Wieder wrote: > > <groan> > > PLEASE don't encourage people to reference objects by id. > > That's the main reason we can't have proper version control in LC. > > If you only use ids as a runtime property (i.e. don't assume they remain > the same across sessions) then that usage has no impact on the > difficulty of having *distributed* version control in LC... > > -- > Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ > LiveCode: Everyone can create apps > > _______________________________________________ > 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
