Is Android clock, which is in the destop, a widget or application (Activity)?

by Dianne Hackborn » Wed, 29 Apr 2009 12:22:34 GMT

Sponsored Links
 Thank-you for your definition of what a widget is.  The current API is what
we have for now.

2009/4/28 caijing <>

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.


Other Threads

1. How to install Android on my PDA

Hi Iam looking for resource that will help to install Android on my PDA
(Imate Kjam) ? can somebody give me a pointer for it ? or is it possible at
all !!!


2. Displaying already existing activities

Hello everyone,

I am trying to display activities that were already created but are
currently in the background. The problem is that I use startActivity
or startSubActivity from the current activity to display them, which
will create a new instance of the background activity. When calling
finish on this new instance, I would want all instances of that
activity to be closed, which is not the case. I could use
launchMode="singleInstance" in the manifest file, but I don't like how
the transition is done between different activities (i.e., when
starting a new activity from my single instance one, an empty screen
is displayed, then the single instance activity is displayed again for
a couple of seconds, then the new (map) activity is shown -- this only
happens when displaying a map activity). If I don't use single
instance on my original activity, the transition is done smoothly.

I tried using an approach mentioned in a previous thread, where I
first have to get the task id for the activity and use that when
trying to bring it to the foreground, but I get the same task id for
every activity that I create. Single instance would have solved that
also, but as mentioned above, I dislike the screen transition

It would have been nice to be able to get a list of all existing
(background) activities and close them manually, but I don't think
it's possible.

If I call finish() write after I start a new activity, an intermediate
screen appears before showing the new activity, which I dislike also.
I am implementing the whole onActivityResult concept, but this goes to
waits (at least in my case) when more than one instance of an activity
is running, since I want all instances to be closed when one is.
Hence, exiting the application has become more cumbersome.

How can I solve this problem?

Thank you,

3. Cross-fading?

4. Logcat stopped working

5. Discussion on media-sample-apps

6. Updating View in a SimpleCursorAdapter

7. Notepad exercise1 - error on import line