A fast, easy to use, free, and community supported 2D game engine
willf
Member
Going through the TMXReadWriteTest sample, I notice that you remove tiles and then you add tiles back. It seems like the code removes and then adds by using setTileGID.
I tried this in my application and what happens is :
Removes Tile Okay
But no tile ever gets put back in there calling setTileGID.
I have to call addTileForGID for it to work. The only difference is that my map is isometric where as the sample is ortho. Is there any reason for this? Am I missing something?
willf
Member
I dug through the source code a bit and I notice that the setTileGID:at: method does a comparison:
unsigned int currentGID = [self tileGIDAt:pos];
if( currentGID != gid ) {
AtlasSprite *tile = [self tileAt:pos];
if( ! tile ) {
tile = [self addTileForGID:gid at:pos];
} else {
CGRect rect = [tileset_ tileForGID:gid];
[tile setTextureRect:rect];
}
// update gid on map
int idx = pos.x + pos.y * layerSize_.width;
tiles_[ idx ] = gid;
}
The method does a comparison for currentGID against the GID you pass in.
In my test I was running i was setting the tile with a GID of 1, then removing the tile with removeTileAt method, then setting the gid back to 1 (using setTileGID:at:). Inside the method it still thinks its currentGID is 1 so it will do nothing, and hence not "add" the tile back.
Should the currentGID be 0 to indicate no tile, since I removed it previously?
IS this an issue with timing? a possible bug? or am I using the tiles in a manner that isn't supposed to be used?
You must log in to post.