What is an ImageAccessor anyways?
I keep thinking the ImageAccessor is the answer to all my problems, and I keep getting disappointed (with all due respect to ddh, it's just the name that's killing me). I keep thinking the ImageAccessor is a onestop shop for all WW objects to access the current imagery at any particular lat lon across all layers. Not too much different than the terrainAccessor.
Alas, it's almost, but no. There has been plenty of discussion about implementing a global mesh and/or a global imagery/texture object -- but the image accessor is not that. (at least for now, in 1.3.3.1)
- Foremost, there is one and only one ImageAccessor per QTS tree, as specified in its QuadTileArgs. Essentially, you should always create a new ImageAccessor before creating a new QuadTileSet.
- It really is just a class to help translate, for any given QTS, the level/row/col tuple for the QTS into a specific filename of an image.
Real Basic.... but for potential to be so much more :-)

0 Comments:
Post a Comment
<< Home