Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could have your layouts in a single xml file. The ones you don't want to see immediately, set <code>android:visibility="gone"</code>in the XML, and at runtime you would do a call to <code>hiddenView.setVisibility(View.VISIBLE);</code>.</p> <p>Your XML would look something like this:</p> <pre><code>&lt;RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="fill_parent"&gt; &lt;LinearLayout android:id="@+id/layout1" android:layout_width="fill_parent" android:layout_height="fill_parent"&gt; &lt;/LinearLayout&gt; &lt;LinearLayout android:id="@+id/layout2" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent"&gt; &lt;/LinearLayout&gt; &lt;/RelativeLayout&gt; </code></pre> <p>at runtime you could do:</p> <pre><code>layout1.setVisibility(View.GONE); layout2.setVisibility(View.VISIBLE); </code></pre> <p>This would essentially create the appearance of the layouts swapping.</p> <p>I believe this would also work if you have shared objects between the two layouts. Just make sure you set the id first using <code>android:id="@+id/view1"</code> and every subsequent setting of this id you would do <code>android:id="@id/view1"</code> (without the +).</p> <pre><code>&lt;RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="fill_parent"&gt; &lt;LinearLayout android:id="@+id/layout1" android:layout_width="fill_parent"&gt; &lt;View android:id="@+id/view1"/&gt; &lt;/LinearLayout&gt; &lt;LinearLayout android:id="@+id/layout2" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent"&gt; &lt;View android:id="@id/view1"/&gt; &lt;/LinearLayout&gt; &lt;/RelativeLayout&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIs it possible to swap XML layouts during runtime in Android?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJoe
    1. USSSZero
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs it possible to swap XML layouts during runtime in Android?
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI like this answer a lot. I personally use a ViewFlipper to manage multiple layouts so that I don't have to manage [Resource] variables coming into scope and out as their layout is set to the content view. Both approaches are viable.
      singulars
      1. PO
      1. USBrad Hein
    2. COAh, I have no experience with the ViewFlipper class. I should check it out next time I need to do something like this.
      singulars
      1. PO
      1. USSSZero
    3. COOh wow that worked perfectly :D Thank you!
      singulars
      1. PO
      1. USjustinl
 

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