3

As you know using rounded coordinates while drawing on canvas is faster. Also floating coordinates may cause unintended gaps on canvas. For example, you are drawing google map tiles to canvas, 256x256 tiles work well, if the starting coordinates are integer. If not, to avoid one pixel unpainted lines, you should round the coordinates.

Here, that's Ok.

But, what if you should use scaling, transformation over canvas, how can you round the coordinates?

e.g.

 ctx.drawImage(image, round(x), round(y), 256, 256);

is OK.

But what if

  ctx.scale(1.0/65536);
  ctx.translate(118079.4);
  ctx.drawImage(image, x, y, 256, 256); // where x and y are integers like 118413

The image will be drawn into floating coordinates. How can I round that coordinates?

user706071
  • 805
  • 3
  • 10
  • 25

1 Answers1

3

The reason that drawing images with floating point coordinates is slow is not because using integers for the coordinates and transformations is faster, but that because of the fraction component of the coordinate the images will be resampled to different pixel positions.

This resampling does not need to happen for images drawn at integer coordinates (with 100% scaling) and is likely a fast path for the image drawing code. If you are doing any scaling, rotation or non-integer translation, the slower image resampling routine may be used.

One way of dealing with gaps between images with floating point coordinates is to make the images slightly larger to cover the gaps, or, render all the visible tiles with rounded coordinates into an hidden un-rotated canvas and then draw that, rotated and scaled, into the visible one.

andrewmu
  • 14,276
  • 4
  • 39
  • 37
  • 1
    Reading your answer here - you write "The reason that drawing images with integer coordinates is slow" you mean "The reason that drawing images with *floating-point* coordinates is slow" right? – Mishax Aug 12 '14 at 12:09