Databases
StackOverflow2013
Postsdbo
POKeeping object's state when user presses "Back" button
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POKeeping object's state when user presses "Back" button
    primarykey
    data
    text
    <p>I have an app in which I programmatically create an <code>EditText</code> view. I assign an ID to that view using <code>setId()</code></p> <pre><code>myEditText.setId(100); </code></pre> <p>so that Android automatically saves that object's state when pausing/stopping the app (as I was advised to do <a href="https://stackoverflow.com/questions/19234653/edittext-not-automatically-saved-on-screen-orientation-change">here</a>). It <strong>works</strong> in these cases:</p> <ul> <li>(1) When I leave the app using the "Home" button: if I then come back to the app, the object's state (displayed text) is restored, as expected.</li> <li>(2) On a screen orientation change (which involves Android automatically destroying the activity and restoring it through a <code>Bundle</code>). The object state is also kept.</li> </ul> <p>However, it <strong>doesn't work</strong> in this case:</p> <ul> <li>(3) When I leave the app using the "Back" button: if I then come back to the app, the <code>EditText</code> object is empty.</li> </ul> <p>Any explanation as to why this happens? Does Android really distinguish between leaving the app with "Home" and with "Back"? According to the <a href="http://developer.android.com/training/basics/activity-lifecycle/recreating.html" rel="nofollow noreferrer">documentation</a>, the object's state should be automatically preserved, through a <code>Bundle</code>, <em>even when the activity is destroyed</em>. And that clearly happens in case (2). But not in case (3)!</p> <p>If this is normal behaviour, how could I have the app's state automatically saved and restored when the user presses "Back"? I know I could use the SharedPreferences for that, but I'd rather have Android do that automatically, just as it does in cases (1) and (2).</p> <p>This happens at least in Android 4.0 and 4.2 (I haven't tested others).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USLuis Mendo
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COuse Shared Preferences to the store the value and restore it. Once you click back button the current activity is popped from back stack and is destroyed. The previous activity in the stack takes focus
      singulars
      1. POKeeping object's state when user presses "Back" button
      1. USRaghunandan
    2. CO@Raghunandan Thanks, but as I said in the question, I'd like to do that without SharedPreferences. Ideally I'd like the same behaviour as with the Home button: Android saving and restoring automatically
      singulars
      1. POKeeping object's state when user presses "Back" button
      1. USLuis Mendo
    3. COthe onDestroy() method is also called after the onPause() and onStop() method while you navigate away from the app using the back button. Please refer to the activity lifecycle for more information.
      singulars
      1. POKeeping object's state when user presses "Back" button
      1. USNiraj Adhikari
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload