Docs: Links added to pages for permissions and configuration activity am: cdfe5e4f55

am: 7a6494aeaf

Change-Id: I907cf418d0a53827a7448135b0d712f41d0024e8
This commit is contained in:
Bert McMeen
2016-06-29 21:59:31 +00:00
committed by android-build-merger

View File

@@ -113,8 +113,8 @@ page.image=/wear/preview/images/complications-main-image.png
<p> <p>
To start receiving complication data, a watch face calls To start receiving complication data, a watch face calls
<code>setActiveComplications</code> within the <code>setActiveComplications</code>, in the
<code>WatchFaceService.Engine</code> class with a list of watch face <code>WatchFaceService.Engine</code> class, with a list of watch face
complication IDs. A watch face creates these IDs to uniquely identify complication IDs. A watch face creates these IDs to uniquely identify
slots on the watch face where complications can appear, and passes them slots on the watch face where complications can appear, and passes them
to the <code>createProviderChooserIntent</code> method (of the to the <code>createProviderChooserIntent</code> method (of the
@@ -283,7 +283,12 @@ android.support.wearable.complications.UPDATE_PERIOD_SECONDS
</p> </p>
<p> <p>
The configuration activity may also be used as an opportunity to request If a data provider needs a specific permission to access a user's data,
then standard code
for runtime <a href="{@docRoot}training/articles/wear-permissions.html">
permissions</a> is needed.
A <a href="{@docRoot}training/wearables/watch-faces/configuration.html">
configuration activity</a> may be used as an opportunity to request
any permissions required by the provider. any permissions required by the provider.
</p> </p>