posted 3 years ago
I would like to know who really calls the onCreate method in android.I know that the super.onCreatemethod is called by the OnCreate method but who really calls the onCreate method in Android?
Here is the code:
Also does android have any starting point as java have(static main entry point)?.From where android really starts it's execution?Could anyone help me.
Here is the code:
Also does android have any starting point as java have(static main entry point)?.From where android really starts it's execution?Could anyone help me.
posted 3 years ago
Yes it has, and it calls onCreate (For Activity classes)
Justin Johns wrote:I would like to know who really calls the onCreate method in android.I know that the super.onCreatemethod is called by the OnCreate method but who really calls the onCreate method in Android?
Here is the code:
Also does android have any starting point as java have(static main entry point)?.From where android really starts it's execution?Could anyone help me.
Yes it has, and it calls onCreate (For Activity classes)
Justin Johns
Ranch Hand
Posts: 32
posted 3 years ago
Check out the details at http://developer.android.com/training/basics/activity-lifecycle/starting.html
Justin Johns wrote:
Also does android have any starting point as java have(static main entry point)?.From where android really starts it's execution?Could anyone help me.
Check out the details at http://developer.android.com/training/basics/activity-lifecycle/starting.html
posted 3 years ago
I think I recall asking something similar a while ago ...
Anyway, if you're using an IDE like Netbeans or Eclipse, its very easy to see who calls a method.
Create a breakpoint, debug the application and have a deek at the call stack.
If you're still a bit curious you can open the java source code and read the comments.
call stack
OP wrote:I would like to know who really calls the onCreate method in android.
I think I recall asking something similar a while ago ...
Anyway, if you're using an IDE like Netbeans or Eclipse, its very easy to see who calls a method.
Create a breakpoint, debug the application and have a deek at the call stack.
If you're still a bit curious you can open the java source code and read the comments.
call stack
