From 20bfe4e68dbdbdb3d726c260b9223f03a3c5df75 Mon Sep 17 00:00:00 2001 From: Michael Chan Date: Mon, 14 Nov 2011 16:44:32 -0800 Subject: Update description of account_type Change-Id: Id929b3a75f86aa79423a0fe0520204ac88502f5b --- docs/html/guide/topics/providers/calendar-provider.jd | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/html/guide/topics/providers/calendar-provider.jd b/docs/html/guide/topics/providers/calendar-provider.jd index 3ab51259a518..d30dda423ec5 100644 --- a/docs/html/guide/topics/providers/calendar-provider.jd +++ b/docs/html/guide/topics/providers/calendar-provider.jd @@ -280,11 +280,9 @@ Calendars.ACCOUNT_NAME}, you must also include {@link android.provider.CalendarContract.Calendars#ACCOUNT_TYPE Calendars.ACCOUNT_TYPE} in the selection. That is because a given account is only considered unique given both its ACCOUNT_NAME and its -ACCOUNT_TYPE. The ACCOUNT_TYPE refers to the way that -the account is being synced. It is often but not always the domain. For -example, an account could be synced through a corporate pop3 sync adapter, in which -case the ACCOUNT_TYPE would not be a domain. There is also a -special type of account called {@link +ACCOUNT_TYPE. The ACCOUNT_TYPE is the string corresponding to the +account authenticator that was used when the account was registered with the +{@link android.accounts.AccountManager}. There is also a special type of account called {@link android.provider.CalendarContract#ACCOUNT_TYPE_LOCAL} for calendars not associated with a device account. {@link android.provider.CalendarContract#ACCOUNT_TYPE_LOCAL} accounts do not get -- cgit v1.2.3-59-g8ed1b