StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16518557
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-05-13T09:17:24.133
FavoriteCount
0
LastActivityDate
2013-09-09T07:24:03.210
LastEditDate
2013-09-09T07:24:03.210
LastEditorUserId
1939564
OwnerUserId
1939564
ParentId
7156752
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
I have implemented my own way of Handling Multiple Screen Resolutions. You could certainly avoid this problem by setting <code>LayoutParams</code> at run time in terms of Percentage The Problem occurs only with <code>Views/Layouts</code> that have some constant width or height lets say <code>280dp</code>. Solution is quite simple if we programmatically set Layout Params of our <code>Views/Layouts</code> in terms of Percentage and only use constant width or height where necessary, elsewhere try to use <code>match_parent</code> to fill up empty space or use <code>weights</code> and define every <code>View</code> relative to other <code>Views</code> this will help your layout to look good in almost every screen resolutions Here is a sample xml <pre><code><?xml version="1.0" encoding="utf-8"?> <RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent" > <LinearLayout android:id="@+id/mLayout" android:layout_width="280px" android:layout_height="300px" /> </RelativeLayout> </code></pre> Notice: I have used px for fixed sized layout's width/height because in <code>LayoutParams layoutParams = new LayoutParams(int width, int height);</code> the <code>width</code> and <code>height</code> take value as pixels Here is an example code of setting width and height in terms of percentage <pre><code>final ViewTreeObserver mLayoutObserver = mLayout.getViewTreeObserver(); mLayoutObserver.addOnGlobalLayoutListener(new OnGlobalLayoutListener() { @Override public void onGlobalLayout() { DisplayMetrics metrics = getResources().getDisplayMetrics(); int deviceWidth = metrics.widthPixels; int deviceHeight = metrics.heightPixels; float widthInPercentage = ( (float) 280 / 320 ) * 100; float heightInPercentage = ( (float) 300 / 480 ) * 100; int mLayoutWidth = (int) ( (widthInPercentage * deviceWidth) / 100 ); int mLayoutHeight = (int) ( (heightInPercentage * deviceHeight) / 100 ); LayoutParams layoutParams = new LayoutParams(mLayoutWidth, mLayoutHeight); mLayout.setLayoutParams(layoutParams); } }); </code></pre> Now might be some people are wondering what is happening here <code>float widthInPercentage = ( (float) 280 / 320 ) * 100</code> Let me explain 280 is the width of my <code>LinearLayout</code> and 320 is the width of my device screen(on which i'm developing), i know currently i'm testing on a device having resolution 320 x 480, what i'm doing is calculating how much area my layout is covering in terms of percentage and then <code>int mLayoutWidth = (int) ( (widthInPercentage * deviceWidth) / 100 )</code> here i'm calculating the new width for my layout according to the screen resolution and by this way your <code>Views/Layouts</code> will look exactly the same on every screen resolution. Conclusion: If you need to set some constant width/height for your <code>Views/Layouts</code> always set value in px in layout file (i.e xml) and then programmatically set <code>LayoutParams</code>. A Suggestion for Google Android Engineers, i guess you guys should seriously think of changing the <code>dp/dip</code> units to <code>percentage</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMultiple screen resolution
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMuhammad Babar
UserOwnerUserId
1. USMuhammad Babar
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CODon't you have a lot of possible errors, since this wont work on ALL the android devices for example the ones running on 3-4 API
 singulars
 PostPostId
 PO
 UserUserId
 USAkshat Agarwal
2. CO@AkshatAgarwal Yes the above solution is tested for **Api 8** and onward.
 singulars
 PostPostId
 PO
 UserUserId
 USMuhammad Babar

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.