#Image resize aspect ratio how to
In this tutorial, you've learned how to make adjustments to the size and display of images. Thus, if you don't call fitCenter() or cropCenter(), Glide will use the specified scale type of the view.įor example, the following ImageView would lead Glide to also use cropCenter as a scale type: Keep in mind that Glide will respect the view's scale type as well. In the section above you always explicitly selected the scale type on the Glide call. We'll look at custom transformations, besides centerCrop() and fitCenter() in a future tutorial. The image will be displayed completely, but might not fill the entire ImageView. centerCrop() // this cropping technique scales the image so that it fills the requested bounds and then crops the extra.įitCenter() is a cropping technique that scales the image so that both dimensions are equal to or less than the requested bounds of the ImageView. override(600, 200) // resizes the image to these dimensions (in pixel) The ImageView will be filled completely, but the entire image might not be displayed. CenterCropĬenterCrop() is a cropping technique that scales the image so that it fills the requested bounds of the ImageView and then crops the extra. It ships with two standard options centerCrop and fitCenter. Glide offers the general scaling options to manipulate the image display. In most of your use cases, you want to prevent this from happening.
Now, as with any image manipulation, resizing images can really distort the aspect ratio and uglify the image display. However, if you know how large the images should be, use override() to provide a specific size. For example, if the app wants to warm up the cache in the splash screen, it can't measure the ImageViews yet. This option might also be helpful when you load images when there is no target view with known dimension yet. override(600, 200) // resizes the image to these dimensions (in pixel). load(UsageExampleListViewAdapter.eatFoodyImages) This will resize the image before displaying it in the ImageView. With Glide, if the image should not be automatically fitted to the ImageView, call override(horizontalSize, verticalSize). Picasso has the same ability, but requires a call to fit(). Glide automatically limits the size of the image it holds in cache and memory to the ImageView dimensions. In comparison to Picasso, Glide is much more efficient memory-wise. Generally speaking, it's optimal if your server or API deliver the image in the exact dimensions you need, which are a perfect trade-off between bandwidth, memory consumption, and image quality.
0 kommentar(er)
