Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>OK, now that you answered that comment I can answer your question feeling more safe about it.</p> <p>What kabuko said is right. However, you're not understanding it because you don't even understand the concept of tasks, and how that relates to the launcher.</p> <p>When you have a <code>singleInstance</code> activity being started at the launcher (see? that's why I asked about your manifest!), the launcher is <strong>not</strong> launching/restarting whatever activities you started/used with Activity A (a <code>singleInstance</code> activity). It's starting/restarting the A's <strong>task</strong> as it was left.</p> <p>In fact, as the documentation says (read kabuko's answer), when you launch B from A, B is considered a new task altogether. It just happens that those two activities are "glued" together in the activity history... obviously, since you start B right after starting A. But I say again: <strong>it's important to see that this constitutes a logical break into your application.</strong></p> <p>And why is that a logical break, you ask?</p> <p>Because A is a <code>singleInstance</code> activity. And as already said here, those are the one and only one activity in that task. So, if you start that <strong>task</strong> again from the launcher, you will end up at A again, and not B since B is another task that does not belong to A.</p> <p>Compare to what you were expecting: if A were a <code>standard</code>, B would be started and considered in the same task. Therefore, restarting A's <strong>task</strong> would end up in B, which is what you were expecting.</p> <p>Finally, as the doc says, this is the reason why you mostly always should not use <code>singleTask</code> and even less <code>singleInstance</code>. Those are not the expected behavior. And since they are not for you, they will be even less for the user, everything else equal.</p>
    singulars
    1. This table or related slice is empty.
    1. POSingleInstance activity make me confuse
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdavidcesarino
    1. USdavidcesarino
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAs I said: if the launcher *had* A as default, the launcher would call A, and the recents would call the activity on top (even B), considering you didn't finish B yet (in this case, would be A). If A is *not* the default/launcher, then the launcher would call B (not A's task, which is different from the launcher's task in manifest) and the recents would call A if that's where you left off. It's all about tasks and the manifest, and the difference between recents and the launcher.
      singulars
      1. PO
      1. USdavidcesarino
    2. COI have post some append question,wish you will tell me more details.:)
      singulars
      1. PO
      1. USuser890973
 

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