OIC I didn’t know he wanted to store the PROPERTIES of the objects. As I have mentioned before I have handlers that can collect the properties of objects and store them in a memory sqLite database. (You can specify a file as well.) But that is not going to help you *quickly* recreate the objects.
Also if you are using Datagrids, the problem becomes considerably more difficult, and in the end no matter what you do, the engine is going to have to recreate every single object so I do not think you are going to save any time, even if you could somehow serialize all the objects on a card. I suppose you could create a template card, then copy / paste that card but the engine is *still* going to have to create the objects. As far as storing an array, it can be stored in the custom property of any group, or it can be saved as a binary file if you first arrayEncode() the array. Bob S > On Oct 16, 2024, at 8:53 AM, Craig Newman via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hi. > > I am confused. As usual. > > "Group them then store the group as an array," > > I read the OP as wanting to gather all the information about all the > controls, not the controls themselves. If so, then the”slow” part is to > gather the data, which has to be done control-by-control, card-by-card and > stack-by-stack. But once through all that, collecting and storing the > information, array or plain, is virtually instantaneous. > > Anyway, how do you store a group as an array? > > Craig > >> On Oct 16, 2024, at 10:54 AM, Bob Sneidar via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Group them then store the group as an array, but placing them won’t be any >> faster methinks. You can also arrayEncode the array first if you need it in >> a serialized format. >> >> Bob S >> >> >>> On Oct 16, 2024, at 7:19 AM, jbv via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> Hi list, >>> >>> Is there a way to catch all controls on a card >>> (for instance) with all their properties and >>> values, and store them in a variable, like >>> innerHML for a DOM element, and have all these >>> controls displayed later very fast and in one go ? >>> >>> I hope I made myself clear. >>> I tried several things, like storing all properties >>> and values as text in a variable and then recreating >>> all controls (quire slow), or duplicate the controls >>> on a hidden card or another stack, but nothing is as >>> easy as what is available i the DOM. >>> >>> Thank you in advance. >>> jbv >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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
