drawable

I am creating a TextView with a drawable underneath, in a GridLayout . I want to bring the drawable to the middle of the TextView ; I tried with setCompoundDrawablePadding(-75) and it only changes the position of the text. Current code: TextView secondItem = new TextView(this); GridLayout.LayoutParams second = new GridLayout.LayoutParams(row2, col1); second.width = halfOfScreenWidth; second.height = (int) (quarterScreenWidth * 1.5); secondItem.setLayoutParams(second); secondItem.setBackgroundResource(R.color.MenuSecond); secondItem.setCompoundDrawablesRelativeWithIntrinsicBounds(0, 0, 0, R

I have this code pb = (ProgressBar) findViewById(R.id.progressBar1); final float[] roundedCorners = new float[] { 5, 5, 5, 5, 5, 5, 5, 5 }; ShapeDrawable pgDrawable = new ShapeDrawable(new RoundRectShape(roundedCorners, null, null)); String MyColor = "#00FF00"; pgDrawable.getPaint().setColor(Color.parseColor(MyColor)); ClipDrawable progress = new ClipDrawable(pgDrawable, Gravity.LEFT, ClipDrawable.HORIZONTAL); pb.setProgressDrawable(progress); pb.setBackgroundDrawable(getResources().getDrawable(android.R.drawable.progress_horizontal)); The problem in this code is that for the progress drawable

I updated my build to build against Android 1.6, and now my bitmaps are scaled down on high density screens. I do NOT want this behavior. I gave this a shot: http://blog.tomgibara.com/post/190539066/android-unscaled-bitmaps but the images are STILL scaling, that is UNLESS I set them to a specific height & width. If I use wrap_content they are scaled down. I have an image loader using the unscaled bitmap loader to create a drawable like so: Bitmap bm = UnscaledBitmapLoader.loadFromResource(imageBufferInputStream); drawable = new BitmapDrawable(bm); which I later assign to an ImageView like so:

Is it valid to use drawable-swdp- like drawable-sw720dp-xhdpi? Below is my scenario: My Acer iconia tab A501 (10") has a resolution of 1280x800 and density mdpi(160dp). It is expected to take the resource from drawable-sw720dp-mdpi. But the resource is being taken from drawable-sw720dp-xhdpi. I have following folders: drawable-sw720dp drawable-sw720dp-mdpi drawable-sw720dp-hdpi drawable-sw720dp-xhdpi is this the way this qualifier is to be used? or Is the density already considered while calculating the smallest width.So should i be having only one folder of the format: drawable-sw720dp I had

This is my problem...: In my activity I have an ImageView and a Button . I want the Button to perform an action ONLY when the ImageView displays a certain drawable. And yes, this means that the ImageView is animating between various drawables that is coded such that it does not interrupt with what I want done. ImageView imgview = (ImageView)findViewById(R.id.imgviewsid); Resources res = getResources(); Drawable acertaindrawable = res.getDrawable(R.drawable.thecertaindrawable); Drawable variabledrawable = imgview.getDrawable(); if (variabledrawable == acertaindrawable) { //does something } It

Ok guys I'm little stacked here. According to official documentation Google says that "Once you've defined your Drawable in XML, save the file in the res/drawable/ directory of your project." is the way to add a XML drawable to the project. But when I created the project ADT created 3 different drawable folders for mdpi, hdpi, and ldpi. So when I wanted to create my XML drawable, I right click on my drawable-hdpi folder and select "Add new Android XML file", and there I have to select what kind of XML file I want to create, but there isn't "drawable" to select. If I create new text file and

I work with several large drawables and I don't know how to manage memory leaks. I tracked the heap size of my application and it doesn't stop to grow (as the allocated memory). It is especially the "byte array (byte[])" type which grows up and never decrease. (in the DDMS Heap view on Eclipse) My application is composed of one activity which uses fragments. Those fragments are displaying several large images. I tried to set drawables callback to null, set drawables to null, clear my volatile cache (which prevent my app from doing too many disk IO) when I pop back a fragment but the heap never