Databases
StackOverflow2013
Postsdbo
POAdd fragments before main activity shows main content view
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAdd fragments before main activity shows main content view
    primarykey
    data
    text
    <h3>Splash</h3> <p>I have main activity UI startup operations that take between 5-10 seconds (that need to be handled on the main UI thread) - so I would like to use a splash screen rather than the default black or non-responsive main UI. </p> <p>A good solution to the splash screen is provided below</p> <ul> <li>which is to first set <code>setContentView(R.layout.splash)</code>,</li> <li>then do the necessary main UI processing (on UI thread but with main view that is not visible)</li> <li>and when that is ready show <code>setContentView(R.layout.main)</code></li> </ul> <p><a href="https://stackoverflow.com/questions/10967532/android-splash-screen-before-black-screen">Android Splash Screen before black screen</a></p> <hr> <h3>Splash with Fragments</h3> <p>I'm also using fragments, which normally require <code>setContentView(R.layout.main)</code> to be called before fragment instantiation - so that the fragment manager could find the view stubs in <code>R.layout.main</code> to inflate the fragments into (<em>strictly speaking view stubs are a different thing</em>).</p> <ul> <li>But I cannot call <code>setContentView(R.layout.main)</code> before creating the fragments, because that replaces the splash screen with the (not-yet-ready) main screen.</li> <li>My fear is that what I want to do cannot be done? </li> <li>Unfortunately, there is no overload like <code>fragmentTransaction.add(viewNotViewId, fragment);</code></li> </ul> <hr> <h3>Almost-Answer</h3> <p>Here's all but the key, which is that <code>setContentView</code> is called before the fragment transactions: <a href="https://stackoverflow.com/questions/5159982/how-do-i-add-a-fragment-to-an-activity-with-a-programmatically-created-content-v">How do I add a Fragment to an Activity with a programmatically created content view</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USCel
    plurals
    1. PL
      singulars
      1. LTLinked
    2. 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. VO
      singulars
      1. POAdd fragments before main activity shows main content view
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAdd fragments before main activity shows main content view
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust out of curiousity: what exactly is it you think you really need to do on the UI thread that may take up to 10 seconds? This is definitely ANR prone and bad for user experience. Adding a splash screen will not suddenly make your app 'responsive' if you don't move the heavy lifting into the background.
      singulars
      1. POAdd fragments before main activity shows main content view
      1. USMH.
    2. CO@MH maybe it is closer to 5 seconds, because i dont see ANR, but the wait is still too long for the user to stare at a blank; the ui is rather custom made out of a lot of data-bound view objects (that once instantiated perform fine)
      singulars
      1. POAdd fragments before main activity shows main content view
      1. USCel
 

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