> -----Original Message-----
> From: L3DT_users_group@yahoogroups.com
> [mailto:L3DT_users_group@yahoogroups.com] On Behalf Of Aaron Torpy
> Sent: Friday, November 18, 2005 10:12 PM
> To: L3DT_users_group@yahoogroups.com
> Subject: RE: [L3DT users' group] SDK progress report
>
> > This only works if you have multiple tiles loaded
> > though, right?
>
> Yes, but the tile-loading is automatic when you
> read/write to a pixel in a tile that's not in memory.
> This means that the program itself (and the user
> too...) doesn't need to specify or even know which
> tiles are loaded. It's all part of the mosaic-map
> magic!

Ah, sounds delicious. The only issue would be if the tile was not local it
would have to be downloaded, causing an additional delay in the overall
process. But at least it would be automatic.

> > I'm not sure if it's a problem in WM actually. I
> think the
> > erosion device is "Explorer Friendly", so it
> shouldn't be a
> > problem.
>
> Oh, I recall reading on the WM forum that strong
> erosion in explorer-mode caused seams/lips at tile
> edges. That was back when WM1.0 was released, so maybe
> there's been an update that I missed.

Ah, no there hasn't been an update since then. It's probably still an issue
in that case. WM's erosion can be pretty extreme though. <G>

- Oshyan