Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>SOLUTION :</p> <p>In my onCreate(), I added the following lines :</p> <pre><code> setContentView(R.layout.mainpage); root = (LinearLayout) findViewById(R.id.mainroot); root.post(new Runnable() { public void run() { Rect rect = new Rect(); Window win = getWindow(); win.getDecorView().getWindowVisibleDisplayFrame(rect); int statusHeight = rect.top; int contentViewTop = win.findViewById(Window.ID_ANDROID_CONTENT).getTop(); titleHeight = contentViewTop - statusHeight; Log.i(Utility.TAG, "titleHeight = " + titleHeight + " statusHeight = " + statusHeight + " contentViewTop = " + contentViewTop); // CALCULATE THE SIZE OF INNER LAYOUTS calculateChildSize(); } }); </code></pre> <p>With the above code, I get the values of titleBar &amp; statusBar. On deducting it from <code>metrics.heightPixels;</code> I get the required height of the screen.</p> <p>Good Point is this code works for all density's.</p> <p>Hope this helps others too.</p> <p>FOR IMPROVEMENT : I have to do similar calculations for all Activities in my application, so was thinking about writing this code only once. I can save teh titleHeight to a static variable so can use in all activities. BUT</p> <p>Can the user change the phone's density at runtime. If so, then the Activity's onCreate will be called again or not ? If not, then can I trap the density change event where I can add this code and make the current activity to refresh. </p> <p>Any idea suggestions for improving is appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid: Get Screen size for the root Layout only
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTvd
    1. USTvd
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid: Get Screen size for the root Layout only
      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
    1. COI don't think the user can change the device density at runtime, although with the introduction of compatibility mode in 3.2 I'm not sure how that would affect it. As for your measurements, if you don't really need the size of the "status bar" and "title bar" but only really want the usable size for your views, then why don't you just do this in your run() method: `run() { sRootHeight = root.getHeight(); }` where `sRootHeight` is a static class variable so your other activities can reference it.
      singulars
      1. PO
      1. USTony Chan
    2. CO@Turbo, I actually got to have 2 rows of 3 buttons each. Based on space available, I calculate the height & width for the buttons considering the spaces between them. I have added 2 rows of 3 buttons each in XML, root.getHeight(); gives me the std sizes of buttons. If the screen is is portriat mode the height is more than width & vice-versa in Landscape mode. Based on the height available I got to set the height of the buttons. If in 3.2 the compatibility moe may be affected to some extend, then in further version, it might be available completely also. What do you say ??
      singulars
      1. PO
      1. USTvd
    3. COI haven't played with the compatibility mode so I'm not too familiar with it's affects. But using the root.post() method of getting your view height is pretty safe I think, since no matter what the screen size, you'll be able to calculate your needed space at runtime. If you are concerned about Compatibility mode [here is how you can disable it](http://developer.android.com/guide/practices/screen-compat-mode.html#Disable)
      singulars
      1. PO
      1. USTony Chan
 

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