Databases
StackOverflow2013
Postsdbo
POShould I rely on Android to discard off-screen draws?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POShould I rely on Android to discard off-screen draws?
    primarykey
    data
    text
    <p>I have a function that takes a seamless bitmap and scrolls it on the screen in any direction using world coordinates. There are 4 draws (play area is smaller than the full bitmap size.. So at the most, you'll see 4 copies of the bitmap, just different sections drawn to retain the seamless effect). What I want to know is, should I apply modifications to the rect bounds so that it's only blitting the parts that it should onto the screen? Or should I let Android handle that? And if I do it myself, how should I handle that? The world coordinates and translate really confuse me, as far as the math goes. :/</p> <p>Here's the code. </p> <pre><code>public void draw(Canvas canvas){ oCoords.x=(int) fX; oCoords.y=(int) fY; oTopLeft = gridContainingPoint(oCoords); oTopRight.x = gridContainingPoint(oCoords).x + iWidth; oTopRight.y = gridContainingPoint(oCoords).y; oBottomLeft.x = gridContainingPoint(oCoords).x; oBottomLeft.y = gridContainingPoint(oCoords).y + iHeight; oBottomRight.x = gridContainingPoint(oCoords).x + iWidth; oBottomRight.y = gridContainingPoint(oCoords).y + iHeight; canvas.save(); canvas.translate(-fX, -fY); oCloud.setBounds(oTopLeft.x, oTopLeft.y, oTopLeft.x + this.iImageWidth, oTopLeft.y + this.iImageHeight); oCloud.draw(canvas); oCloud.setBounds(oTopLeft.x + this.iImageWidth, oTopLeft.y, oTopLeft.x + (this.iImageWidth * 2), oTopLeft.y + this.iImageHeight); oCloud.draw(canvas); oCloud.setBounds(oTopLeft.x, oTopLeft.y + this.iImageHeight, oTopLeft.x + this.iImageWidth, oTopLeft.y + (this.iImageHeight * 2)); oCloud.draw(canvas); oCloud.setBounds(oTopLeft.x + this.iImageWidth, oTopLeft.y + this.iImageHeight, oTopLeft.x + (this.iImageWidth * 2),oTopLeft.y + (this.iImageHeight * 2)); oCloud.draw(canvas); canvas.restore(); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSalx
    1. USSalx
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POShould I rely on Android to discard off-screen draws?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POShould I rely on Android to discard off-screen draws?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POShould I rely on Android to discard off-screen draws?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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