On 20/01/13 00:50, Michael Bedward wrote:
Yep, the standard JAI TiledImage class keeps all of its tiles in
memory - that's why DiskMemImage was created.
Sorry - no suggestions for what might be happening with batik and the
different rendering results.
interestingly for DiskMemImage, it
On Sun, Jan 20, 2013 at 9:40 AM, Ákos Maróy a...@maroy.hu wrote:
On 20/01/13 00:50, Michael Bedward wrote:
Yep, the standard JAI TiledImage class keeps all of its tiles in
memory - that's why DiskMemImage was created.
Sorry - no suggestions for what might be happening with batik and the
On 20 January 2013 21:09, Andrea Aime andrea.a...@geo-solutions.it wrote:
Hmm... labels are always drawn last, wondering if with bigger images the
tiles are getting swapped to disk, and
when they are retrieved back to draw the labels for some reason they are not
writable anymore.
Just a
On 20/01/13 11:14, Michael Bedward wrote:
On 20 January 2013 21:09, Andrea Aime andrea.a...@geo-solutions.it wrote:
Hmm... labels are always drawn last, wondering if with bigger images the
tiles are getting swapped to disk, and
when they are retrieved back to draw the labels for some reason
OK - I've just run a test here where a small DiskMemImage is created
having 4 tiles, using a DiskMemTileCache that can only hold a single
tile in memory. The test gets a Graphics object for the image and
draws into each tile in turn It then draws into the tiles again, in
the same order as before.
Michael,
OK - I've just run a test here where a small DiskMemImage is created
having 4 tiles, using a DiskMemTileCache that can only hold a single
tile in memory. The test gets a Graphics object for the image and
draws into each tile in turn It then draws into the tiles again, in
the same
following up on this:
so, it seems to me that while the position of the text to be drawn is
within the image bounds (image bounds being 2666x1751, drawing
transformation coordinates being 2527, 608), but the selected tile is
wrong (tileX: 0, tileY: 0, where each tile is 1024x1024 in size -
Michael,
I seem to have solved the issue, please see a patch attached to this ticket:
http://code.google.com/p/jaitools/issues/detail?id=215thanks=215ts=1358704047
Best regards,
Akos
--
Master Visual Studio,
I love it when bugs get fixed while I'm sleeping peacefully :) Thanks
for your great detective work Akos - very much appreciated. The patch
looks good.
The jaitools sources and issues were moved to GitHub last week so I've
copied your Google Code issue there:
On 21/01/13 01:37, Michael Bedward wrote:
I love it when bugs get fixed while I'm sleeping peacefully :) Thanks
for your great detective work Akos - very much appreciated. The patch
looks good.
thank you!
The jaitools sources and issues were moved to GitHub last week so I've
copied your
On 21 January 2013 18:28, Ákos Maróy a...@maroy.hu wrote:
and committed your fix:
https://github.com/mbedward/jaitools/commit/master
excellent. would this mean that this would appear in the -SNAPSHOT
version of jaitools soon, through maven repositories?
Hi Ákos,
Yep - the 1.3 snapshot jars
11 matches
Mail list logo
