That's good to hear. I was worried it might either be a design decision
or a technical limitation. Is there an open bug/enhancement report I can
subscribe to to be notified of progress on this (and if not, should I
open one)?
It also might be nice (and apologies if this already exists) to have a
function of some sort called the givenPermissions or something similar,
that lists all the permissions that have been granted. A similar
function, say the blockedPermissions could maybe list ones that have
been asked before but not granted. Or even just have the
blockedPermissions, which would be checked by the app when using a
device feature. If that feature has been explicitly blocked by the user,
do something else, otherwise use the feature as intended and let the
underlying system deal with permission requests.
Just a thought, really. I couldn't see "androidRequestPermission" in the
dictionary so I am not sure what is/isn't available at the moment.
On 24/08/18 23:11, Monte Goulding via use-livecode wrote:
Yes it hasn’t been done yet but adding a similar api to the new handlers to the
android-utils module is probably the most sensible so it can be reused easily.
_______________________________________________
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
