On Apr 20, 12:06 pm, "Mark Murphy" <[email protected]> wrote:
> > On Apr 20, 11:03 am, Jean-Baptiste Queru <[email protected]> wrote:
> >> The proper way would be to start the relevant activity. I don't know
> >> whether the specific Intent to start that activity is documented as
> >> part of the public API, though.
>
> >> JBQ
>
> > Doesn't it seem like enormous overkill (cpu/memory/cycles) to launch
> > an activity to persist one simple setting?
>
> It would appear SDK applications are not presently capable of providing a
> UI to do that, because thepropertiesare read-only from the perspective
> of SDK applications (per Mr. Guy's email). Hence, today, launching the
> built-in activity may be the only available option.
>
> If you would like thosepropertiesto be read-write to SDK applications
> (perhaps governed by a permission), post an issue tohttp://b.android.com
Thanks for the link Mark :).
Hans
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
