Esdras Beleza wrote:
> 5) Here comes the problem: if I go to other application (browser, for
> example) and go back to my application, the intent seems to be received
> again, onResume() is called and the dialog A, B or C is shown. But they
> must be shown *only* when the widget is clicked.
>
> Any
On 8 May 2010 10:08, Mark Murphy wrote:
> Esdras Beleza wrote:
> > I don't know if I understood your advice, but I tried some things like
> > that.
> >
> > I tried to put new data into the intent (like a "used" flag) and
> > updating the intent with setIntent(updatedIntent). I also tried to
> > c
Esdras Beleza wrote:
> I don't know if I understood your advice, but I tried some things like
> that.
>
> I tried to put new data into the intent (like a "used" flag) and
> updating the intent with setIntent(updatedIntent). I also tried to
> create an useless new intent and replace the applicatio
On 8 May 2010 05:39, blew wrote:
> You may want to update your intent with the latest app state just
> before the user leaves your application.
> That way your onResume will work with the most up-to-date intent:
> Either the one from updated by your widget or the one updated by your
> app itself.
You may want to update your intent with the latest app state just
before the user leaves your application.
That way your onResume will work with the most up-to-date intent:
Either the one from updated by your widget or the one updated by your
app itself.
On May 8, 12:25 am, Esdras Beleza wrote:
5 matches
Mail list logo
