Sorry to clutter up the thread. The overlapping tile suggestion may not work properly. Intra-tile zIndex priority will be preserved. Inter-tile zIndex priority may not be. It will depend on the childNode order of the CANVAS element which is arbitrary. Sorry.
Also, the repaint can occur in the CANVAS tile itself. Just one detached CANVAS element is required to restore the original CANVAS tile. Both "getImageData" & "putImageData" are too inefficient to be practical. Conversion between 32 bits & 128 bits is performed for each pixel. It depends on transfer direction. CPU architecture (big endian / little endian) determines whether bytes have to be reordered. "drawImage" ought to be very quick if the rectangle dimensions are identical. It is just one REP MOVSD per row of pixels. Perhaps the DMA processor can assist. Because one of the CANVAS elements is in memory but off screen, old graphics card may not be able help. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
