# textview Published articles for textview. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Controlling TextView MinWidth DevFeed: [Controlling TextView MinWidth]() Original publisher: [Read original article]() Published: 2021-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Android](), [constraintlayout](), [Code]() Tags: [android](), [android-layout](), [background](), [constraintlayout](), [gravity](), [layout](), [properties](), [textview](), [xml]() ### AI overview A technical explanation of how Android TextView minimum-width APIs interact. Setting minWidth or minimumWidth alone may not reset a dimension declared in XML; both properties must be cleared, and a background can still impose a minimum width. ### Source excerpt Introduction Sometimes we might need our TextView with wrap_content width to occupy more space than it will based on amount of characters it displays. For that we can set minimum width. Usually, we do that via XML like this: Having setup like this we ensure that our TextView will occupy a minimum of 200dp. Also, we can control minimum width programmatically via: TextView#setMinWidth. But controlling minimum width programmatically has one caveat that I'd like to describe below. ## Avoiding fake italic and bold text on Android DevFeed: [Avoiding fake italic and bold text on Android]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2019-12-18T00:08:59Z Content type: tutorial Language: en Sources: [Saket Narayan]() Topics: [Android](), [Font](), [formatting]() Tags: [android](), [fonts](), [formatting](), [legibility](), [textview]() ### AI overview This Android typography tutorial explains that fake bold and italic styling is produced when the platform cannot find the requested font variant. It describes the resulting effects on visual differentiation and legibility, and recommends applying the complete font family so true variants can be selected. ### Source excerpt Changing line heights in Android using LineHeightSpan has this ugly side-effect where the cursor ends up being very tall, extending till the full line height instead of just the text height. I've decided to go to extreme lengths to fix this over the next few days. For science. pic.twitter.com/2tWLvDq1rz -- Saket Narayan (@Saketme) November 24, [...] The post Avoiding fake italic and bold text on Android appeared first on Saket Narayan. ## Displaying HTML tags on TextView the right way DevFeed: [Displaying HTML tags on TextView the right way]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2017-06-29T12:59:12Z Content type: tutorial Language: en Sources: [Saket Narayan]() Topics: [HTML](), [Android]() Tags: [android](), [html](), [spans](), [textview]() ### AI overview A tutorial explaining how Android parses and displays HTML in TextView. It compares TextView#setText(), Resources#getString(), Html.fromHtml(), and Html.fromHtml() with CDATA, emphasizing CharSequence and span objects as the mechanisms for rendering styled text. ### Source excerpt While going through the codebase of a former client, I found that I was using four different ways for showing HTML on Android. This made me realize that I didn't really know what the correct way of showing them is and I've always hammered my way using trial & error until the HTML tags have showed up. Embarrassed, I decided to explore how [...] The post Displaying HTML tags on TextView the right way appeared first on Saket Narayan. ## A dive into Async-Await on Android DevFeed: [A dive into Async-Await on Android]() Original publisher: [Read original article]() Author: Niek Haarman Published: 2016-11-03T16:09:29Z Content type: tutorial Language: en Sources: [Stories by Niek Haarman on Medium]() Topics: [async/await](), [Kotlin](), [Coroutines](), [Code](), [ui](), [Network](), [Database]() Tags: [android](), [android-app-development](), [async](), [asynchronous](), [await](), [blocking](), [callback](), [compiler](), [coroutines](), [database](), [kotlin](), [kotlin-compiler](), [main-thread](), [network](), [textview]() ### AI overview This tutorial explains async-await on Android using Kotlin coroutines, focusing on handling long-running network and database operations without blocking the UI thread. It contrasts nested callbacks with suspension functions such as asyncUI and await, and describes how the Kotlin compiler transforms the code. ### Source excerpt Note: this article was written for a preview version of coroutines for Kotlin. Its details have changed since then. In a previous article I provided a glimpse into the world of async-await on Android. Now it's time to dive a little bit deeper in this upcoming functionality in Kotlin 1.1 What is async-await for? When dealing with long-running operations like network calls or database transactions, you need to make sure you schedule this work to a background thread. If you forget to do this, you may end up with blocking the UI thread until the task is finished. During that time, the user cannot interact with your application. Unfortunately when you schedule a new task in the background, you cannot use its result directly. Instead, you're gonna have to use some sort of callback. When that callback is invoked with the result of the operation, you can continue with what you want to do, for example run another network request. This easily flows in what people call a 'callback hell': multiple nested callbacks, all waiting to be invoked when some long-running task has finished. fun retrieveIssues() { githubApi.retrieveUser() { user -> githubApi.repositoriesFor(user) { repositories -> githubApi.issueFor(repositories.first()) { issues -> handler.post { textView.text = "You have issues!" } } } } } This snippet of code does three network requests, and finally posts a message to the main thread to update the text of some TextView. Fixing this with async-await With async-await, you can program that same function in a more imperative way. Instead of passing a callback to the function, you can call a suspension function await which lets you use the result of the task in a way that resembles normal synchronous code: fun retrieveIssues() = asyncUI { val user = await(githubApi.retrieveUser()) val repositories = await(githubApi.repositoriesFor(user)) val issues = await(githubApi.issueFor(repositories.first())) textView.text = "You have issues!" } This snippet of code still does three n ## A better way to handle links in TextView DevFeed: [A better way to handle links in TextView]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2016-09-11T17:48:21Z Content type: tutorial Language: en Sources: [Saket Narayan]() Topics: [Android](), [App]() Tags: [android](), [browser](), [google-maps](), [library](), [textview]() ### AI overview The article explains problems with Android's default LinkMovementMethod for clickable URLs in TextView, including incorrect touch areas, unreliable highlighting, and limited customization. It introduces BetterLinkMovementMethod as a drop-in replacement with custom URL-handling support. ### Source excerpt There are two ways of "linkifying" URLs in a TextView. First, as an XML attribute: and second, programmatically: TextView textView = (TextView) findViewById(R.id.text1); Linkify.addLinks(textView, Linkify.PHONE_NUMBERS | LINKIFY.WEB_URLS); In both the cases, the framework internally registers a LinkMovementMethod on the TextView that handles dispatching a ACTION_VIEW Intent when any link is clicked. This is why phone-numbers open in a dialer when clicked, [...] The post A better way to handle links in TextView appeared first on Saket Narayan. ## The power of TextView (Part 1): Drawables DevFeed: [The power of TextView (Part 1): Drawables]() Original publisher: [Read original article]() Published: 2014-01-30T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [ui](), [XML]() Tags: [android](), [code](), [layout](), [lint](), [properties](), [textview]() ### AI overview This Android tutorial explains how TextView compound drawables can place images beside text using drawableLeft, drawableRight, drawableTop, drawableBottom, and drawablePadding. It shows how this approach can replace a LinearLayout and ImageView, reducing layout complexity and simplifying XML. ### Source excerpt Everything Android, Kotlin and other random topics ## Android Tips: Making a Custom Button out of Anything DevFeed: [Android Tips: Making a Custom Button out of Anything]() Original publisher: [Read original article]() Published: 2013-03-19T07:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [Large Screen]() Tags: [android](), [interface](), [java](), [layout](), [textview]() ### AI overview This Android tutorial explains how to create custom buttons with both images and text without relying on complex layouts or invisible overlays. It describes using a LinearLayout with clickable behavior and button-state backgrounds as an alternative to the standard Button and ImageButton classes. ### Source excerpt The Android APIs are filled with things that don't quite seem right. I've always been annoyed by the lack of relationship between interface elements. For instance, isn't a ListView really just a special case of a GridView with only one column? Yet GridView and ListView aren't directly related, so we get oddities where I can add header and footer views to a ListView, but not a GridView. One thing that seems to trip people up is the Button class. Android has a Button class for text (and images if your not really concerned with formatting them) and an ImageButton class for images. Like the ListView/GridView situation mentioned earlier, these two buttons are not, in fact, related. Button inherits from TextView and ImageButton inherits from ImageView.