On Android the stack is in the engine folder that is read-only. It resides in the apk(a zip formatted file). The engine folder is virtual and read only. If you want to modify a stack it needs to be a separate stack that you move to the documents folder. Any file that you want read/write must be moved from the assets folder to the documents folder(or SD card). I use an SQLite database in the documents folder for user data but a text file would work also.
Ralph DiMola IT Director Evergreen Information Services [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, June 01, 2012 12:21 PM To: [email protected] Subject: Re: Android: custom prop vs. .txt? Nicolas Cueto wrote: > I have an Android app that uses a small amount of data (under 10Kb). > The data gets updated regularly. Haven't decided when. > Perhaps every half-second, or perhaps when the user hits the hardware > home-button. > > Right now, the data is stored both as a custom prop of the card and as > a .txt file. Maybe, though, I can just rely on .txt? Or would the > Android device and/or OS for some reason prefer I use "write to txt" > as little as possible? Perhaps to save energy? > Perhaps because it's slower than saving to a custom prop? "Saving"? Issuing a save command to the stack with the props should take slightly longer than writing the data to a file, but with only 10k the difference will be negligible. If you don't need to save often then using custom props will provide good efficiency and simple, robust behavior. - rg/4w _______________________________________________ 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 _______________________________________________ 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
