I'm also seeing similar, strange behavior using tiled bitmaps. 

I'm building for Honeycomb, and have a number of Views with backgrounds 
defined in the following selector drawable:

<?xml version="1.0" encoding="utf-8"?>
<selector xmlns:android="http://schemas.android.com/apk/res/android";>
    <item android:state_pressed="true" 
android:drawable="@drawable/tiled_bitmap_1" />
    <item android:drawable="@drawable/tiled_bitmap_2" />
</selector>

Here are the two xml resources for the tiled bitmaps:

<?xml version="1.0" encoding="utf-8"?>
<bitmap xmlns:android="http://schemas.android.com/apk/res/android";
    android:src="@drawable/tile1"
    android:gravity="clip_vertical" 
    android:tileMode="repeat" />

<?xml version="1.0" encoding="utf-8"?>
<bitmap xmlns:android="http://schemas.android.com/apk/res/android";
    android:src="@drawable/tile2"
    android:gravity="clip_vertical" 
    android:tileMode="repeat" />

tile1 and tile2 are the same size, both in the same drawable-hdpi folder. On 
all views, tiled_bitmap_2, the default state drawable, always tiles 
correctly. tiled_bitmap_1 (the pressed state drawable) tiles correctly on 
some views, but not on others.

Strangely, if I switch tiled_bitmap_1 and tiled_bitmap_2 in the background 
selector, both backgrounds always tile correctly. If I change tiled_bitmap_2 
to another tiled bitmap - tiled_bitmap_3 - in the project, the tiling works 
correctly. But I then tried copying the xml for tiled_bitmap_3 into a new 
file, tiled_bitmap_3_copy, and used that copy as the pressed state drawable, 
and the tiling for the pressed state became inconsistent. Even though the 
two xml files are identical!

Anyone have an idea on what could be causing this behavior?

Mike

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to