hello, Julien!

how can I help you today?

Hi mark, first of all your book is fantastic, second year i buy it.

thanks!

I need some help, i have a notification, when a user click on it, i want to display an alert dialog on top of my activity. But only when we come from the notification.

The problem i have is screen rotation

when i rotate the screen, the same intent is lunch and the dialog is shown

I don't really want that. I just want my dialog on a click on the notification.

where are you displaying the dialog? onCreate()?

yes

the Bundle passed into onCreate() will be null when your activity is initially created and non-null after a configuration change (such as a screen rotation)

hence, only display the dialog when the Bundle is null

ok i will try that

The same problem occurred when i launch an activity from history (long press on home button) (activity previously launched by the click on the notification)

that will not be helped by the Bundle trick

is your current code always displaying the dialog? or are you examining something about the Intent to decide whether to display the dialog?

i examine the action of the dialog

which i set on the intent of the pendingintent

of the notification

do you mean the action of the Intent?

yeah the action of the intent sorry

the problem is that the Intent action is part of the history and therefore will be used by the recent tasks list

I partially resolved this issue checking the flags

to know if it comes from history

another possibility is to simply not have it be part of the history, via android:noHistory="false" on the <activity>

yet another possibility is to cheat a bit and use a boolean value in a static data member

call it doWeNeedTheDialog

set it to false when you initialize it

interesting

have your PendingIntent actually route to a BroadcastReceiver, which sets it to true before starting the activity

your activity shows the dialog if true, plus sets it to false

since your process isn't going to be terminated in that short window, you should be safe

good idea

and the data is totally transient, not part of history or anythihng

er, anything

it would also solve your configuration change issue

but, it's a bit of a hack

Actually the same problem occurred when the screen goes of and on.....

that too would be handled by this hack

Yes

So i guess for my scenario

i need to use this hack

to be sure that the dialog shows up only on a click on the notification

and not on all the other time watever happens

it's certainly one option

Do you think there is an 'android official way' of doing that ?

take care of all scenario ?

if I knew of one, I would have suggested it instead of this hack :-)

yeah dumb question ^^

is there anything else that I can help you with?

Yes

I have an activity with a FragmentPagerAdapter and a ViewPager, in the getItem of the adapter i instanciate my Fragment and keep a reference in a field of my activity.

is this field holding *all* the fragments? presumably you have more than one page in the pager

No just one specific field for one specific fragment i need to interact with

oh, OK

Could i assume in onResume of my activity

that my fragment will be not null

?

I do not think that this is a safe assumption, though it may work for the current version of ViewPager

ok

I am assuming that you are creating the adapter in onCreate() of the activity

yes

in this figure : http://developer.android.com/guide/components/f...

we got the activity state in front of fragment state

and the resumed state of the activity

seems to imply that the fragment is instanciated

But actually i have ran some test

and when i call programmatically finish() on my activity, and restart it

my field is null

that diagram assumes that the fragment is being instantiated in onCreate() of the activity

you are not doing that, based on your description

you are having the FragmentPagerAdapter create this fragment

which may or may not happen during onCreate() of the activity

why that ?

in onCreate i instanciate my adapter

because you have no real control over when getItem() is called

yes

hence, getItem() *might* be called during onCreate(), or it might not

this is the problem i thought about..

if you *really* need this one special fragment created in onCreate(), do so yourself, and have the FragmentPagerAdapter use it

yes you right

thanks a lot, it really helps !

you are very welcome

good evening, time to go to bed for me. Thanks again ! BYE

bye!