Thank you, though its wierd, when setting a 9 patch image as a button
background with setBackgroundResource(R.drawable.Filename) it's like
1.5 doesn't want to 9patch it or something, the image goes huge and
make the button bigger, where as 1.6 and higher leave the button size
along. Oh well, I got
Jeffrey,
Use "-v4" suffix with alternate drawable folders to make them invisible
to Android 1.5.
So you'd have:
res/drawable
res/drawable-ldpi-v4
res/drawable-hdpi-v4
"V4" means only use if API version is equal to or above "4", which is
Android 1.6 with proper hdpi/ldpi handling. Android 1.
That would make sense except that it tries to draw the image from
drawable-nodpi before trying drawable. Also, the error isn't that the
image is missing, it's that the image must be bigger than a 0 x 0
image, which it is. For some reason 1.5 trying to read a 9patch from
nodpi causes it to mess up.
In 1.5 "nodpi", "hdpi", "mdpi" and "ldpi" doesn't exist. This terms
were born in 1.6 so probably 1.5 doesn't recognize this folders.
On 14 mayo, 07:36, Jeffrey wrote:
> Slight update, it turns out taking the resource out of the nodpi
> folder caused it to revert to the drawable folder and then it
Slight update, it turns out taking the resource out of the nodpi
folder caused it to revert to the drawable folder and then it worked.
Does anyone know why putting it in the nodpi would cause it to mess
up? fyi the image in question is actually the default button image,
taken out of the sdk resourc
5 matches
Mail list logo