Bob, good point. In my case I am using several standalone stacks, so when the standalone opens, it reads data from a remote location (database or Google Sheets) and saves them as custom variables. In addition there are variables that are created throughout a session that are saved in a similar way. Then these values are available to all stacks throughout the session. Glad to hear of any thoughts on this.
On Tue, 10 Mar 2020 at 14:54, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > The downside to doing this is that you cannot have your properties persist > between sessions unless you can save the stack containing the properties. A > mainstack in a standalone cannot be saved, and other stacks may have issues > saving if they are in a sandboxed or secured location. > > If you are using this just for runtime variables, that would work but it > begs the question, why? Variables are easier to reference in your code. > > Bob S > > > > On Mar 10, 2020, at 03:38 , Kaveh Bazargan via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Absolutely. I keep most of my variables in stack custom properties. > > > _______________________________________________ > 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 > -- Kaveh Bazargan PhD Director River Valley Technologies <http://rivervalleytechnologies.com/> • Twitter <https://twitter.com/kaveh1000> • LinkedIn <https://www.linkedin.com/in/bazargankaveh/> _______________________________________________ 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