pete at mollysrevenge.com
Fri Feb 18 16:37:16 CST 2011
Are we talking about saving data between runs of the standalone or just re-opening the stack in the same run of the standalone? As other have pointed out, there is no way to save data between runs of a standalone without the usual workaround they mentioned. But I think datagrids have a "persistant Data" property that affects whether the data in them is saved when the stack they are in is closed and then re-opened in the same run.
Not sure what's happening with your follow up email about the dg not being populated, that sounds very weird.
-------------- next part --------------
On Feb 18, 2011, at 11:28 AM, DunbarX at aol.com wrote:
> This came up in the forum, trouble saving a datagrid in a standalone. I glibly told the original poster that there should not be any issue.
> To test I made a splash stack and a substack; the usual. The substack has a datagrid, a field and a button. The button put random numbers
> into both the datagrid (via setting the dgText) and the field. The stacks are saved on closeStack.
> After making the standalone, clicking the button loads data. But only the field data is saved. I checked back in the standalone
> settings, and wonder if either I am missing something there, or datagrids do not save at all. The forum thread had evolved to having to save the
> datagrid data in an external file, and reloading next session. That seems unfair.
> Craig Newman
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode