Are you just asking why you are required to call super.onCreate()? If so,
you are required to call the super class of that and onStop() and onResume()
and others just to prevent apps from forgetting to call the base class
implementation and causing them to break when the platform changes in the
future and does stuff in those implementations.
On Tue, Jun 14, 2011 at 6:39 AM, Android herle.san...@gmail.com wrote:
The Reason we use onCreate(savedInstanceState) because, upon
super.onCreate() it will reach the Activity (parent class of any
activity) class to load the savedInstanceState. (beacause the demo
activity class we have created is not capable of loading the saved
state) Yeah, we normaly don't set any saved instance state, but
android framework made such a way that, we should be calling that.
Please correct me if i am wrong.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
Dianne Hackborn
Android framework engineer
hack...@android.com
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.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
