- TextInputLayout Styling
- Hint color
- Label, Helper and Error
- Fonts
- Spaces
- Bottom line color
- Box background-color
- Cursor and Selection
- TextInputLayout with a drawable without the padding Hint
- Removing TextInputLayout extra top padding
- 6 Answers 6
- TextInputLayout hint overlap issue
- 6 Answers 6
- TextInputLayout
- Стилизация
- Обработка ошибки
- Счётчик символов
- TextInputEditText
TextInputLayout Styling
Today, with the material components, we have at least 3 out of box implementations of input layout: Default, FilledBox, and OutlinedBox. And we want to briefly walk through their styling:
If you are looking for a brief solution you can use this table. Below you can find the description of each of these parameters in detail.
Hint color
Hint color could be set via “android:textColorHint” parameter of TextInputLayout. This parameter also changes the label default color (label focused color could also be changed in other ways). Let’s set a purple color (#673AB7) as an example.
Label, Helper and Error
Such parameters as “app:hintTextAppearance”, “app:helperTextTextAppearance” and “app:errorTextAppearance” together with all the necessary text parameters of styles.xml should be used to customize labels, helpers and errors in TextInputLayout. The parent of the text appearance style should be TextAppearance.AppCompat or some of its children.
Also, please keep in mind the following:
- “ app:hintTextAppearance” affects the focused label color and label size in any state;
- when an error is shown, the bottom/border line will have the color indicated in the “android:textColor” parameter of errorTextAppearance. This color will be changed to the default once the error is removed.
Here is the TextAppearances for error and helper that was used in the above shown TextInputLayouts:
Fonts
Fonts of all elements except inputted text (label, hint, error, and helper) could be easily changed in the program via the typeface parameter of TextInputLayout. We have done it in the following way:
Spaces
Label’s, Helper’s and Error’s spaces are connected to the EditText in the TextInputLayout. So, to increase or decrease spaces between the error/helper messages and bottom line/border you should use “android:layout_marginBottom” parameter, between the label and the top of the text, or add some space on the start of the error, helper and the label, and you should set positive or negative padding to the EditText. But you should understand that this will affect the text inside the InputLayout so, it would be better if horizontal spaces were symmetric from both sides.
As an example, let’s increase space above the errors for Default and OutlinedBox input layouts and decrease for FilledBox input layout. Also, let’s add some extra space at the start of the input layouts.
Bottom line color
Bottom line color could be changed with “app:backgroundTint” attribute of EditText view. Pay attention to the prefix, “app:” that makes this parameter back-compatible and useful even for Android API 16.
As for the OutlinedBox, it does not have the bottom line but has an outline instead. To change its color we should use “app:boxStrokeColor” parameter, but this parameter changes stroke color in the focused state only. Changing the default state of the stroke is a bit tricky. We should override mtrl_textinput_default_box_stroke_color color. The line below should be added to the color.xml file:
Let’s make the bottom line and the outline stroke color purple (#673AB7) as well.
Box background-color
This element is present in Filled and Outlined input layouts and can be changed via “app:boxBackgroundColor” parameter. Let’s change this parameter to the transparent purple (#26673AB7) only for FilledBox input layout.
Cursor and Selection
Finally, we get to the most interesting part — how to change the cursor and the selection handles. Most of you have already tried to use “app:textSelectHandle” parameters, that allow changing the drawable of the cursor handle and selection left and right handles. But how to change the color without drawing custom drawables and without changing the main application colors? It is not the secret that the cursor and handles color, as well as label color in focus mode, take their color from the AppTheme “colorAccent”. Of course, we can change it for the whole project but it is not obligatory. We can just use ThemeOverlay and change the “colorAccent” for a single view. We should inherit our style from ThemeOverlay.AppCompat and set it as the “android:theme” parameter of the view and that is all. As for the selection highlight, you can change it via android:textColorHighlight of the EditText.
In the example above was used android:color/holo_blue_light:
So, my final layout looked like this:
colors.xml includes the following colors:
styles.xml includes the following styles:
Tap the 👏 button if you found this article useful!
About the Author
Dmytro is Android Developer at OmiSoft, whose inner perfectionist does not allow to be content with mediocre results but forces him to move forward to excellence.
Need an Android mobile app with clean & maintainable code? Click here to get an estimate! Or find us on Facebook and Twitter.
Источник
TextInputLayout with a drawable without the padding Hint
Sometimes you need a custom view
In the office, we are building a new app, and the UI team build a layout a little different to what I was expecting, if your UI team build something like this for you, don’t worry, everything is possible in the software world. So let’s get started. This is the layout we are going to build today:
If you are a fast thinker you will go for the obvious solution for the first part of the Layout, you will put a TextInputLayout and a TextInputEditText inside of it, with the right margins and font sizes.
What about the second one? You probably will put a drawableLeft inside a secondary TextInputEditText and a drawablePadding to archive this layout, but this is probably not the correct way to go, ‘cause once you put the drawable and the hint goes to the top of the TextInputLayout, will have padding just after the drawable you set.
After thinking a little I thought we should make a custom view that should extend TextInputLayout and make a couple of modifications to a couple of classes.
This view will work, no matter the drawable size, the first step start on the init() function that we have, inside the TextInputLayout class we are going to search for the object called collapsingTextHelper, this is a secondary class that is in charge of put the hint at the top of the view.
Inside the CollapsingTextHelper class, we can notice that we have access to the rect functions to make the calculations for space in the hint, inside this class, we are going to search for the filed collapsedBounds which is a Rect Object in charge of drawing the title.
And finally, we are going to look for the function called recalculate, that is almost self-explanatory, make the recalculations for the parts of the view
After making this changes over our init function in our custom view, we need to make a couple of changes onLayout function that will go exactly after onMesure and before onDraw, onLayout will assign a size and position to all of its children.
Finally, you should implement your class like this:
If you have any question, feel free to reach me out
Happy Coding 👩🏻💻
Источник
Removing TextInputLayout extra top padding
TextInputLayout seems to always have some extra padding at the top (no matter that all margins/paddings are set to 0):
The layout looks like:
How to remove this extra space?
6 Answers 6
You can remove extra space above AppCompatEditText by setting app:hintEnabled=»false» to TextInputLayout but it won’t display hint until you re-enable that.
Checkout below code
Hope this helpfull..
The accepted answer didn’t work for me on version — 1.2.1 so I did some experiments and realized that the padding doesn’t actually come from the TextInputLayout , rather it’s from TextInputEditText . So first I removed the padding from that, but it looked uneven, so I set custom padding to TextInputEditText and it worked fine. Just add this line android:padding=»16dp» to the TextInputEditText replacing 16dp with your desired value.
having a structure like this:
app:errorEnabled=»false» in TextInputLayout
You can use this
You can do it by overriding the default padding style of TextInputStyle, (Material version should be above 1.1.0)
Источник
TextInputLayout hint overlap issue
I’m using TextInputLayout from Android Design Library to show label on EditText.
The problem is when I start activity with that EditText hint (label) text overlaps the actual text (for a second) and only then returns to its own place (at the top of the EditText).
To illustrate this issue I recorded a short sample video: https://youtu.be/gy0CzcYggxU
Here is my activity.xml:
6 Answers 6
I came up with a cheap workaround for this and another bug.
Subclass the TextInputLayout
See code for addView()
If you have text set in the text view when it is inflated it will set the hint to collapsed and prevent an animation. This code performs a workaround that will temporarily set text until the state is set during setup. As a bonus there is code that makes sure the hint gets drawn just in case there is only one layout pass.
The workaround that worked for me was to update activity like this:
Finally found the adequate explanation of the issue:
Well it turns out that there was a performance optimization added to the framework in Android 4.0 which allowed your view hierarchy only one single draw pass before the Activity animation was started. Once the Activity animation has ended, your view hierarchy is drawn every
16ms as you expect.
TLDR: it is platform limitation and this behavior will occur on older versions (Marshmallow and lower).
On Nougat animation will run as expected without the lag.
Источник
TextInputLayout
Макет TextInputLayout сначала появился в библиотеке Android Design Support Library и добавляет немного красоты к текстовому полю. Когда пользователь начинает вводить текст в текстовом поле, то подсказка, заданная в этом компоненте, всплывает над ним в специальном TextView. Пример можно увидеть на видео.
Библиотека больше не развивается, поэтому используйте AndroidX, которую я и буду теперь использовать в описании.
Компонент можно найти на панели инструментов в разделе Text.
При добавлении компонента через визуальный редактор автоматически добавляется дочерний элемент TextInputEditText.
Так выглядел компонент в составе Support Library.
Подсказку не обязательно указывать в атрибуте android:hint у текстового поля. Можно программно присвоить через метод:
Стилизация
В AndroidX у компонента появились новые стили: OutlinedBox, FilledBox. Можете самостоятельно запустить пример с двумя стилями и посмотреть на отличия.
Далее идёт текст для старой версии статьи. Вам следует самостоятельно обновить нужные фрагменты кода.
Общая стилизация доступна следующим образом. Пропишем стили в styles.xml:
Обработка ошибки
Предыдущий пример показывал применение подсказки. Но также можно выводить сообщения об ошибке. Здесь потребуется написать немного кода. За вывод ошибки отвечает атрибут app:errorEnabled. Назначим текстовому полю тип клавиатуры и однострочный текст. При наборе текста после нажатия на клавишу Enter проверяем длину текста. Если текст меньше четырёх символов, то выводим сообщение об ошибке.
Текст ошибки выводится снизу от текстового поля.
Стиль для сообщения об ошибке можно стилизовать. Добавим новый атрибут.
В файле стилей res/values/styles.xml добавим новый стиль:
Теперь выводится другим цветом.
Расширенный вид стилей:
Применяем через атрибуты app:errorTextAppearance и android:theme.
Счётчик символов
С помощью атрибутов app:counterEnabled и app:counterMaxLength можно установить счётчик символов с указанием предела, который будет выводиться под текстовым полем.
Когда будет превышен лимит, то цвет счётчика изменится. Этот цвет можно стилизовать через стиль.
Стиль применяется к атрибуту app:counterOverflowTextAppearance:
TextInputEditText
Казалось бы простой компонент, никаких трудностей не возникает. Но не торопитесь. Стоит повернуть устройства в альбомный режим, как текстовое поле растянется на весь экран и никакой подсказки вы не увидите. Возможно, это баг, который когда-нибудь починят. Но проблему легко решить, если вместо стандартного EditText использовать специальный компонент из библиотеки TextInputEditText:
Источник