Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COHello Michael - Many thanks for your information. What I am failing to understand at this point is how to set up resources correctly (i.e. using dip etc). I just assumed that you could just scale up an image in Photoshop or whatever for hdpi. I don't understand how you can change the dip in Photoshop. Basically all I need is an explanation of what goes in which directory and what size. E.g. a 320x480 image on a G1 in 'drawable' works fine. To get get it to work on say a Droid, what size and where do I put it? The documentation does seem to contradict itself.
      singulars
    2. COUsing dip is an internal android thing. Essentially what you are doing internally in Android when specifying 10 dip, is to tell Android to make the object 10 pixels on a standard screen, but 15 pixels on a high resolution screen (I forget the exact numbers, but I think it is x1.5). In general, you should go through all your layouts and make sure that you always use dip/dp and not px for your sizes.
      singulars
    3. COIn general, you should not use a "drawable" directory. There is a bug in one of the Android versions (I forget which, but it is either 1.6 or 2.0) that makes it pick the wrong resources if the "drawable" directory exists. The best setup, I've found, is to use explicit "drawable-mdpi" and "drawable-hdpi" directories. Resources that you place in the drawable-hdpi directory will be used as is - not scaled. So your 320x480 graphic in mdpi should be upscaled to 480x800/850 in the hdpi resources. If a graphic is not available for hdpi, android will try to get the resource from mdpi and upscale it.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload