From fa9b5cae646ab1461c9f0f4b170c941e3da7c740 Mon Sep 17 00:00:00 2001 From: Dianne Hackborn Date: Mon, 30 Jan 2012 11:45:00 -0800 Subject: Update documentation to reflect the old approach not working. The old approach has a problem with the original application's recent tasks entry disappearing (this is probably a bug in the platform). Update to an alternative approach that does work. Change-Id: I15e582eff8c77cc22628f7b099e9f04eb5bfbce7 --- .../guide/topics/ui/notifiers/notifications.jd | 24 +++++++++------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/docs/html/guide/topics/ui/notifiers/notifications.jd b/docs/html/guide/topics/ui/notifiers/notifications.jd index 33b0fecc9ed5..bef9671100bf 100644 --- a/docs/html/guide/topics/ui/notifiers/notifications.jd +++ b/docs/html/guide/topics/ui/notifiers/notifications.jd @@ -245,31 +245,27 @@ an application to be part of that application's UI flow, so simply launching the activity like this can cause it to be mixed with your normal application back stack in undesired ways. To make it behave correctly, in the manifest declaration for the activity the attributes -android:launchMode="singleInstance" and +android:launchMode="singleTask", +android:taskAffinity="" and android:excludeFromRecents="true" must be set. The full activity declaration for this sample is:

{@sample development/samples/ApiDemos/AndroidManifest.xml interstitial_affinity} -

Because of the use of singleInstance, you must be careful about launching -any other activities from this one. These activities will be launched -in their own task, and care must be taken to make sure this interacts -well with the current state of your application's task. This is essentially +

You must be careful when launching other activities from this initial activity, +because this is not a top-level part of the application, does not appear in +recents, and needs to be relaunched at any point from the notification with new data +to show. This best approach is to make sure any activity launched from it is +launched in its own task. When doing this care must be taken to make sure this +new task interacts well with the current state of your exiting application's +task. This is essentially the same as switching to the main application as described for the Email style notification shown before. Given the makeMessageIntentStack() -method previously shown, handling a click here would look something like this:

+method previously shown, handling a click then would look something like this:

{@sample development/samples/ApiDemos/src/com/example/android/apis/app/IncomingMessageInterstitial.java app_launch} -

If you don't want to use the singleInstance launch mode for -this activity, an alternative approach is to use android:taskAffinity="". -This tells Android that the activity should not be treated as part of the -main application flow, so it will not get mixed together with that. All of the -other issues discussed here do still apply, though this would allow you to start -additional activities that are part of this notification task instead of switching -to and replacing the main application task.

-

Managing your Notifications

The {@link android.app.NotificationManager} is a system service that manages all -- cgit v1.2.3-59-g8ed1b