StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12343086
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-09T21:20:02.440
FavoriteCount
0
LastActivityDate
2012-09-09T21:20:02.440
LastEditDate
LastEditorUserId
0
OwnerUserId
769265
ParentId
12340001
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You seem to have trouble with some basic Android behaviour. First of all, when the user presses the HOME button, he isn't exiting your application, he is just putting your application in the background so that he can go do something else. He doesn't expect your application to exit if he does this. In fact, when he returns to your application he expects to find it in exactly the same condition as when he left it. This is standard Android behaviour and you shouldn't change that unless you have a really good reason to. Secondly, when the user presses the BACK button, Android automatically finishes the current activity and returns to the previous activity in the activity stack. This is standard Android behaviour and you don't need to write anything special to make this happen. From looking at your code you have activity <code>TunnelsActivity</code> that starts activity <code>Cgt</code>. <code>TunnelsActivity</code> does not call <code>finish()</code> when it starts <code>Cgt</code> so the activity stack will have <code>TunnelsActivity</code> on the bottom and then <code>Cgt</code> on the top when that activity is running. in <code>Cgt</code> you are catching the BACK button and the HOME button and calling <code>onStop()</code>. This is definitely wrong. You should never call <code>onStop()</code>. <code>onStop()</code> is called by Android as part of the Activity lifecycle in certain situations. Calling <code>onStop()</code> will not make your activity go away nor will it make your application exit. All it will do is confuse Android. Also, when Android calls <code>onStop()</code> it expects the code to call through to <code>super.onStop()</code> which your code isn't doing. This will cause the code to throw an Exception, which may be why you are seeing your activities getting restarted. I suggest removing your <code>onStop()</code> method and removing your <code>onKeyDown()</code> method. That may solve all your problems.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy does my android apps activitie reopen when I close my app
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDavid Wasser
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy does my android apps activitie reopen when I close my app
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.