.@Simeon
Could you add the Codea in-app player’s “pause” functionality to the runtime in order to accommodate using the system photo picker? I’m working on an app idea right now that pretty much requires a photo picker.
I was thinking maybe we could call some built-in function that triggers the runtime to pause execution, then resume execution after a photo is picked or the modal picker is canceled.
Is this at all feasible without re-architecting the runtime?
.@bwyatt that’s feasible, so long as pause() is called from Objective-C code (otherwise, if you call it from Lua code, there would be no way to unpause, as it would stop executing your Lua code).
.@Simeon
Thanks for the quick response. You’ve made a great point there. I wonder if the runtime could handle it almost like a breakpoint. The runtime assumes control there, takes care of the picker, then hands control back to the Lua code and resumes its execution.
The function (in Codea) would probably need to have a callback for when no image is returned, and maybe also one for when one is returned.