bobs at twft.com
Fri Feb 18 16:57:36 EST 2011
If you mean that the datagrid is in the mainstack of the standalone, I think you will find that NO data ANYWHERE is saved in that stack. The mainstack becomes a part of the standalone, and as such is read only. No way around this. Not for LiveCode standalones, not for Microsoft Word docs (if they were made into standalones that is).
The ONLY way to have data in a stack persistent between standalone sessions is to make the stack either a substack of some other mainstack (like a splash stack) or else a supporting file, in which case it will get put in a folder inside the standalone bundle (for mac) and I don't know where Windows will put it, but the upshot is, the standalone will act like a runtime engine when it opens your now editable substack.
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