Android :: 1x1 Size Nine-patch Image Not Showing Up On Emulator Device
Oct 29, 2010
I'd like to use a 1x1 size Nine-patch image from Android drawable resources. When I'm trying to display it with <ImageView> in my layout xml file, this one is never showing up on the Android emulator device. Here's the xml code below. Code...
I have an ImageView which I want to always be the same size. If the image is smaller than the view, I'd like it to be centred in the view. If the Image is larger than the view then I'd like it scaled down - with aspect ratio preserved.I've had several attempts at this myself
I'm trying to create on of these images, but Eclipse won't accept it once I've used the draw9patch tool. I've found other people having the same problem, and saw this comment: I discovered later that the problem I was having was caused by the image not being exactly true to the nine-patch spec as defined in the documentation. Once I fixed the image to have a clean (i.e., no gradients etc) one pixel border it was fine. "'m not much good when it comes to image design. What does this mean, how do I create my original png file to meet the specification for Nine Patch?
I have an image with a fixed size , ex. 300 x 300 ; it was a background image of my view. But my view size was dynamic , so i need an image which can stretch , according to desired size. can any one tell me how to make it ? I know we have to use nine oatch drawable ? i don't know how to tool given with android sdk ? can any one tell me how to make image to png?
I am trying to use a nine patch image as a background in an android game. The image expands well in multiple resolutions but, my game has slowed down by 10 fps. I used to get a consistent 45 to 50 fps now I get 35 fps. The question is when we use a nine patch as a drawable and set it as a background in a view does it have any performance implications as opposed to a plain bitmap drawing.
i have list views with image views and text views etc in them, and i'm trying to fix up a situation where the background image of a list element changes in the "pressed" state. if there's a straightforward way of doing that, please let me know! right now, i override onTouchEvent() in the topmost view, and also in those child views who don't just delegate to their parents which would be image views. i have to check for long clicks myself, but basically this scheme works. the list views are potentially different sizes depending on how much text is in the views etc, so i thought i would use a 9-patch as the background. however, when the background changes from flat white to the 9-patch, this seems to indent the view a bit - ie give it margins. eh? if i change the image to a non-9-patch, the margins remain as they are. i've tried different sizes of 9-patch, from 320x150 or so down to 100x30 etc, no change. what's going on?
So I'm loading images from a web service, but the size of the images are sometimes smaller or bigger than other images and the visualization looks silly when I put them in a ListView in android. I'd like to fix the size of my ImageView so that it only shows a portion of the image if it's larger than a preset amount. I've tried everything I can think of setting the setMaxWidth/setMaxHeight, setting the scale type to centerCrop, using ClipableDrawable wrapping my BitmapDrawable, setting using Drawable.setBounds(). I've tried setting in the XML and programmatically, but neither worked. I'm very surprised setting max width/height didn't do anything. Below is the XML I'm using ImageView definition in my layout file
And several other attempts to call "link" that also fail (sshfs does not support hard links).
Is it possible to change the emulator's behavior to create lock files somewhere in /tmp (using some hash of image path as lock file name)? I am OK to try this myself: which repositories from https://android.git.kernel.org/ are necessary to rebuild the emulator alone, and where in the sources is the code responsible for image locks?
I'm using the android plugin for eclipse, and when I try to run my program using a real device through the android device chooser, my phone is not listed as a device. I have updated eclipse and all of the android packages, but it still isn't showing up. My phone is running 1.6, which is also the target version listed in the eclipse project.Also, the reason I decided to try testing on a real device is because the emulator doesn't seem to be working right anymore when I run my project. The emulator launches, but the program never does. Any ideas?(using windows 7/t-mobile mytouch 3g)
Does anybody have an idea what I may be doing wrong. I have installed the usb drivers and have my device running in debugging mode but when I run my basic hello world application through eclipse my device wont show up in the device chooser. I have also tried re installing the sdk and all the drivers and still no luck.
I have developed and tested my app on the emulator, and now want to install it on my HTC device. the apk installs successfully, however my database is not going with it. I have created my database using sqliteman browser b/c I have to insert a bulk data before the app starts. I have four tables in my db and call each in different activities and created all on the sqliteman. after the data is inserted I pull back the db onto the data folder of the emulator. it works perfect on the emulator but failed on the device. when I try to pull my db on the real device, it shows access denied problem
I have created a custom icon bar in Android using the XML layout creator, using a RadioGroup within a LinearLayout (XML included below). Each RadioButton within the RadioGroup has a custom drawable (with checked and unchecked states) as its android:button attribute. The Linear layout is itself within a RelativeLayout so that it can appear at an arbitrary position on the screen (as a side bar, in this instance).The drawables are 55 pixels wide, and the android:layout_width attribute of all these views is "wrap_content".When I make this component visible, aligned to the bottom-left of the screen, only about three-quarters of the RadioButton image widths are visible. Setting the layout_width of the RelativeLayout to "fill_parent" rectifies this and causes the full button to appear.However this means that the button group consumes click events across the entire width of the screen. How can I make the entire button appear, and have only the area of the button respond to clicks? Hard-coding the width of the drawable is not a particularly desirable solution.<RelativeLayout android:id="@+id/RelativeLayout01" android:layout_width ="wrap_content" android:layout_height="wrap_content"> <LinearLayout android:id="@+id/LinearLayout02" android:layout_width="wrap_content" android:layout_height="wrap_content" android:orientation="vertical" android:layout_alignParentBottom="true" android:layout_alignParentLeft="true" android:layout_below ="@+id/LinearLayout01" android:visibility="invisible"><RadioGroup android :id ="@+id/ RadioGroup01" android:layout_height="wrap_content" android:checkedButton="@+id/RB01" android:layout_width="fill_parent"> <RadioButton android:id="@+id/RB01" android:layout_width="fill_parent" android:layout_height="wrap_content" android:button="@drawable/DR01"/><RadioButton android:id="@+id/RB02" android:layout_width="fill_parent" android:layout_height="wrap_content" android:button="@drawable/DR02"/> <RadioButton android:id="@+id/RB03" android:layout_width="fill_parent" android:layout_height="wrap_content" android:button="@drawable/DR03"/> <RadioButton android:id="@+id/RB04" android:layout_width="fill_parent" android:layout_height="wrap_content" android:button="@drawable/DR04"/> </RadioGroup></LinearLayout>
Is there a limit to the size of the .apk file when using it on the emulator. When I run the default app created while creating a project, the .apk file size is about 5K and it runs ok. When I try to run a real app which uses other application libraries so that the total size is about 325K, I get the following error: Failed to upload Benchmark.apk on device 'emulator-5554' java.io.IOException: Unable to upload file: timeout Launch canceled! I had increased the heap size of emulator to 64 MB and RAM size to 192 MB.
Has anyone tried to do a tcp client server app using the emulator using the pc as a server and the phone as the client?I've got a bit of an issue where its only sending one packet, ie 1491 bytes of data regardless of how much there actually is to send, from the client(Phone) to the server(PC).
Is there a way to set the emulator's internal storage size? It is currently set to a fairly low value. Also, while searching for the answer to this question (which I didn't find), I ran across several threads which seemed to indicate that many phones have a very limited amount of internal storage. If I have an application which is 30 Mb (due to graphics and audio resources), is this going to be too large for most people to use. Should I be looking to install my application on the SD card instead (can this only be done on version 2.2 systems?).
I added -scale 0.2 to the Default emulator option under eclipse and launched the emulator.After that I got a really small window. I then removed the -scale 0.2 but the emulator window remains small.I can start the emulator from command line and i get the normal size, but not with eclipse.Any help would be appreciated.
I have an image that I want to place on the background on my activity. For the G1 I would use a background of 320x480 but with the nexus 1 the resolution is almost double that. Should I just place the large image and make the smaller phones size down? I am trying to keep the size of my package down as much as possible.
I was trying to use some of the new camera methods included in Froyo, i.e. setPreviewCallbackWithBuffer() & addCallbackBuffer(). In the documentation it's said you need first to create a buffer of appropriated size and use the addCallbackBuffer() method. The buffer size must be width * height * bits_per_pixel or otherwise you'll never receive a preview frame. To know the image size, you can ask to the camera about it's configuration. When I'm trying to configured the camera I use Camera.getParameters().getPreviewSize() the emulator says the size is 320*240, but with that size it didn't work on emulator. I used the old setPreviewCallback() and, in the onPreviewFrame(), I asked the size again. That time the size was 480*320. Then I hard- coded that values in the first code and everything worked. Now I'm afraid not only the emulator would have that behavior. Unfortunately I don't have any real device with Froyo and I can't try it. So, anyone have tried that methods in real devices? btw, are they really increasing the poor performance and frame rate?
When I try to push a 40MB file onto the sdcard adb hangs and the emulator freezes. Is there a file limitation that I am not aware of? I couldn't find anything on this. When I try the same with a smaller file it works without problems. I have configured the sdcard of the emulator device to have a size of 512MB and when I check with adb shell df I see that there is enough space.