Colin, Sorry I didn't even notice your message til just now.
For persistent data, you're going to need some form of storage. Usually, websites utilise cookies. This is the more security-conscious way of handling it, depending on the data of course. w3school.com/js/js_cookies.asp has good examples on how to do this. So you can call a bit of js from LiveCode to read or write it where necessary. Use sparingly. 'Wait' is documented not to work. The best way to put a 'wait' in place is to split up your handler and use 'send blah to thisScript in x seconds'. 'System date' has no meaning because you are talking entirely to the browser via JS (effectively), not the users' system. The other date forms work fine. What use case do you have that needs the 'system date'? Maybe you could set a user preference for the format if necessary. All the best Sean On Fri, 27 Mar 2020 at 20:46, Colin Holgate via use-livecode < use-livecode@lists.runrev.com> wrote: > I made progress getting the basic stack going, the main hold ups were > ‘wait' and 'the system date', neither of those work. > > What approach is needed if the stack has text entry that you want to > persist when the page is reloaded? Save this stack seems not to work. > _______________________________________________ > 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
