First, I am adding Gridview and second i add imageview in the gridview, but the layout can't show up the image。
Does anyone know what the problem could be?
Thank you very much!!
Simply change the height and width attributes :)
Don't drag, use xml text editor instead. And as mentioned above use height and width appropriate.
Android Studio shows you a warning, next to the ImageView (yellow warning icon). If you hover over this, it will tell you what the problem is. (most likely missing height and width)
I want to remove the corner radius from the card view.
I tried this:
card:cardCornerRadius="0dp"
card:cardElevation="0dp"
but no change.
Is it possible to do this?
Remove card_view:cardCornerRadius attribute from xml and try again.
No need to assign it 0dp.
Use app:cardCornerRadius="0dp"instead of card:cardCornerRadius="0dp"
I need to add a scrollable android TextView, which will show alot of text.
I want to achieve this kind of effect:
But I found no way of doing so.
Is there any good way of doing it?
Thank you!
try below properties to TextView
android:requiresFadingEdge="vertical"
android:fadingEdgeLength="32dp" //To change the gradient overlay height
The most convient way of doing this is creating a drawable. You can either make your own image in the image editing software of your choice or create a GradientDrawable. Make sure the colors go from white to transparent. Then place this drawable on top of the textview near the bottom.
Why new created constraintLayout does not have android:id="#+id/constraint_layout_file_name"?
After creating new constraintLayout we suppose to go to Design view and start creating our layout. But when we do so and we add to our layout for example a TextView, place it where we like and provide constraints so it stays like this after pushing layout on a device it will not stay where we want it to be. It will appear on left top corner on a device because constraints we provided have error
The id "constraintLayout" is not defined anywhere.
What we have to do is to manually add android:id="#+id/constraint_layout_file_name" and edit all constraints. Example:
wrong constraint:
app:layout_constraintLeft_toLeftOf="#+id/constraintLayout"
corect one:
app:layout_constraintLeft_toLeftOf="#+id/constraint_layout_file_name"
Reason why I do ask is that it took me too much time to figure out what I'm doing wrong and I think I'm not the only one.
i had the same problem.
and when i turned on the Autoconnect (on the top | left side) it fixed it by changing it
from:
app:layout_constraintLeft_toLeftOf="#+id/constraintLayout"
to:
app:layout_constraintLeft_toLeftOf="parent"
first,compile 'com.android.support.constraint:constraint-layout:1.0.0-beta4';
second,sync your project!
I would like to define the z order of the views of a RelativeLayout in Android.
I know one way of doing this is calling bringToFront.
Is there are better way of doing this? It would be great if I could define the z order in the layout xml.
The easiest way is simply to pay attention to the order in which the Views are added to your XML file. Lower down in the file means higher up in the Z-axis.
Edit:
This is documented here and here on the Android developer site. (Thanks #flightplanner)
If you want to do this in code
you can do
View.bringToFront();
see docs
Please note, buttons and other elements in API 21 and greater have a high elevation, and therefore ignore the xml order of elements regardless of parent layout. Took me a while to figure that one out.
In Android starting from API level 21, items in the layout file get their Z order both from how they are ordered within the file, as described in correct answer, and from their elevation, a higher elevation value means the item gets a higher Z order.
This can sometimes cause problems, especially with buttons that often appear on top of items that according to the order of the XML should be below them in Z order. To fix this just set the android:elevation of the the items in your layout XML to match the Z order you want to achieve.
I you set an elevation of an element in the layout it will start to cast a shadow. If you don't want this effect you can remove the shadow with code like so:
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
myView.setOutlineProvider(null);
}
I haven't found any way to remove the shadow of a elevated view through the layout xml.
I encountered the same issues: In a relative layout parentView, I have 2 children childView1 and childView2. At first, I put childView1 above childView2 and I want childView1 to be on top of childView2. Changing the order of children views did not solve the problem for me. What worked for me is to set android:clipChildren="false" on parentView and in the code I set:
childView1.bringToFront();
parentView.invalidate();
Please note that you can use view.setZ(float) starting from API level 21. Here you can find more info.
Thought I'd add an answer since the introduction of the
android:translationZ
XML field changed things a tad. The other answers that suggest running
childView1.bringToFront();
parentView.invalidate();
are totally spot on EXCEPT for that this code will NOT bring childView1 in front of any view with a hardcoded android:translationZ in the XML file. I was having problems with this, and once I removed this field from the other views, bringToFront() worked just fine.
API 21 has view.setElevation(float) build-in
Use ViewCompat.setElevation(view, float); for backward compatibility
More methods ViewCompat.setZ(v, pixels) and ViewCompat.setTranslationZ(v, pixels)
Another way collect buttons or view array and use addView to add to RelativeLayout
childView.bringToFront() didn't work for me, so I set the Z translation of the least recently added item (the one that was overlaying all other children) to a negative value like so:
lastView.setTranslationZ(-10);
see https://developer.android.com/reference/android/view/View.html#setTranslationZ(float) for more
Or put the overlapping button or views inside a FrameLayout. Then, the RelativeLayout in the xml file will respect the order of child layouts as they added.
You can use custom RelativeLayout with redefined
protected int getChildDrawingOrder (int childCount, int i)
Be aware - this method takes param i as "which view should I draw i'th".
This is how ViewPager works. It sets custom drawing order in conjuction with PageTransformer.
Check if you have any elevation on one of the Views in XML. If so, add elevation to the other item or remove the elevation to solve the issue. From there, it's the order of the views that dictates what comes above the other.
You can use below code sample also for achieving the same
ViewCompat.setElevation(sourceView, ViewCompat.getElevation(mCardView)+1);
This is backward compatible.
Here mCardView is a view which should be below sourceView.