On 8/12/17 8:27 AM, Mark Waddingham via use-livecode wrote:
Indeed, working like that means that suspend and resume aren't really that 
relevant - the engine already turns off the things you need to when suspended 
and turns them back on when it resumes.


There's a major problem if the user issues the "quit" command on Android. The engine removes all libraries in use when that happens, but the OS leaves the app in RAM. When the app next resumes, libraries aren't there and all calls to library functions silently abort.

<http://quality.livecode.com/show_bug.cgi?id=19297>

--
Jacqueline Landman Gay         |     jac...@hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
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

Reply via email to