Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For the first screen, i would use a seperate activity. CaseyB's answer is really good, and it is actually how I hand it as well (now, when you have alot of orientation changes, and a few things on the backstack, you'll get forcecloses, but its inevitable). What I would do is the first screen, make it its own activity, then call a second FragmentActivity and make the fragment on the Left side static (meaning define it in XML). That way you dont have to worry about it. Then, you can focus on the right fragment. If you set the setRetainInstance, then you dont need to worry about recreating the views. But, if it goes to the backstack, then you lose everything. It never calls onDestroy, only onDetach. And onCreate is only called the first time the fragment is created. So, I would avoid using onCreate at all, and focus on using onActivityCreated() and onAttach() to instantiate values and whatnot</p> <p>Update - Use the onCreate() method to set setRetainInstance(true) and call your JSON and network code to create the views. Its important to do it here, so that it only gets called once. This should work entirely for orientation changes and going back and forth between fragments (the backstack will work, just you cant set it to retainInstance while in the backstack. That was a typo on my part). </p> <p>Then, any other code you want called when the fragment is brought back up, use onAttach() since onCreate() wont be called since it was never destoryed</p> <p>Then, in order to get control of your items again, you cant use getActivity().findViewById(), you have to use this.getView().findViewById(). I dont know why that is the case (since you would think that it would be attached to the activity viewgroup, but it isnt). That should be the only hiccup you should hit. Outside of that, it should work perfectly fine. </p>
    singulars
    1. This table or related slice is empty.
    1. POsetRetainInstance(true); doing it wrong?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USShaun
    1. USShaun
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POsetRetainInstance(true); doing it wrong?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COThanks again Shaun. I follow you up to the point of *make the fragment on the Left side static (meaning define it in XML).* When you start getting into the backstack I get lost. If you want to add a simple implementation of how I could use `setRetainInstance()` in the actual fragment once the views are loaded I will accept it as the correct answer
      singulars
      1. PO
      1. USi_me_mine
    2. COIf you need further help, send me an email at compguru910atgmail . I can send you a simple project to illustrate it a little better.I had alot of problems with this too when I first started working with fragments.
      singulars
      1. PO
      1. USShaun
    3. COe-mail sent. If you don't mind, can you invite me to chat? I have a couple quick questions right now I could bounce off you.
      singulars
      1. PO
      1. USi_me_mine
 

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