On 10/27/17 6:17 AM, Peter Reid via use-livecode wrote:
The following folderIdentifier values are supported:• "documents": The folder where application-specific data can be placed (typically valuable) • "cache": The folder where transient application-specific data can be placed (typically not valuable) • "temporary": Same as "cache" • "engine": The (virtual) folder containing the application's LiveCode engine and other resources that were copied into the application at build time • "resources": Same as "engine". • "external documents": The folder on the primary shared/external storage device where application-specific data can be placed • "external cache": The folder on the primary shared/external storage device where transient application-specific data can be placed • "external temporary": same as "external cache" Note: If using any external folderIdentifier values, ensure you have the 'Write External Storage' permission checked in the application standalone settings --------- The above implies that access to the internal filing system is read-only, even for the "documents" special folder and that the only filing system that I can write to is the external one on the SD card. Is this correct?
Actually, only the engine folder is read-only. All the others are read/write and you should be able to save files to those. It would be helpful if you could post an example of a file path that fails.
-- Jacqueline Landman Gay | [email protected] HyperActive Software | http://www.hyperactivesw.com _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
