Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is available in the bitmap itself -- <a href="http://developer.android.com/reference/android/graphics/Bitmap.html#getDensity" rel="nofollow">http://developer.android.com/reference/android/graphics/Bitmap.html#getDensity</a>()</p> <p>If you are loading this through the higher level Resources.getDrawable() API, you won't have a Bitmap but just an abstract Drawable. If you can guarantee the resource will always be a bitmap (not a nine patch or other such thing), you can cast this to a BitmapDrawable and get the Bitmap from that.</p> <p>If you are doing this for production code, I would be a little uncomfortable with this since generally an app should either let the framework take care of density, or take care of it all itself (by for example putting the bitmaps in drawable-nodpi). If you are playing games with bitmaps base on loaded density, you may shoot yourself in the foot. Or you may be fine, since I don't really know what you are doing. :)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to determine what bitmap resource was loaded (ldpi, mdpi, or hdpi)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UShackbod
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to determine what bitmap resource was loaded (ldpi, mdpi, or hdpi)?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. I am loading through getResources(), R.drawable and it will always be a bitmap. If this ends up in prod is yet to be determined. Depends on what I learn before then. If the framework always picks the correct density, I won't have to do as much, but I didn't want to assume it was bug free, so I wanted to verify it picked what I expected based screen dimensions. If it didn't, I'll scale it myself and set some values, so I can calculate locations of the bitmaps on the screen. There are some other reasons I want this info, but I am running out of characters that I can type in this comment.
      singulars
      1. PO
      1. USMike
    2. COYou wouldn't want to scale it yourself -- the framework will automatically scale a drawable (including the dimensions reported to you) based on the density of its bitmap in relation to the device (or target Canvas) density. There are a lot of subtle things done to ensure that a drawable in a density different than the density the app is working in will behave as if it is in the app's density. This is fundamental to things like the density compatibility code that ensures applications written before 1.6 still work on device with different density screens.
      singulars
      1. PO
      1. UShackbod
    3. COOne of the reasons I thought about doing this is when I had a background bitmap that was 480 x 800 and I tested it on a 480 x 854 display, there was a gap at the bottom. In other words, it didn't scale it automatically to that screen. As soon, as I put code in to scale it myself, it looked fine. Are you saying it was supposed to scale automatically to the 480 x 854 screen?
      singulars
      1. PO
      1. USMike
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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