Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 1ada3fb1 authored by Bert McMeen's avatar Bert McMeen Committed by android-build-merger
Browse files

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

Docs: Links added to pages for permissions and configuration activity am: cdfe5e4f am: 7a6494ae am: ae5a14bc
am: 7379e4a3

Change-Id: I2ce8bbe060db184c26cc2a44478985c26d31e4dc
parents b8a7ddad 7379e4a3
Loading
Loading
Loading
Loading
+8 −3
Original line number Diff line number Diff line
@@ -113,8 +113,8 @@ page.image=/wear/preview/images/complications-main-image.png

    <p>
      To start receiving complication data, a watch face calls
      <code>setActiveComplications</code> within the
      <code>WatchFaceService.Engine</code> class with a list of watch face
      <code>setActiveComplications</code>, in the
      <code>WatchFaceService.Engine</code> class, with a list of watch face
      complication IDs. A watch face creates these IDs to uniquely identify
      slots on the watch face where complications can appear, and passes them
      to the <code>createProviderChooserIntent</code> method (of the
@@ -283,7 +283,12 @@ android.support.wearable.complications.UPDATE_PERIOD_SECONDS
    </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.
    </p>