Question

SOLUTION:

Simply separating the method call
Tile *tile = [[Tile alloc] initWithX:x Y:y];
into two separate lines such as:
Tile *tile = [Tile alloc];
[tile initWithX:x Y:y];
caused the method to stop receiving the ints as memory pointers. I’m baffled as to why this occurred but it fixed the problems. Any explanations as to why this happened would be appreciated. Thanks to all for the help!

ORIGINAL POST:

This is a bit of a weird question as I’ve run into this problem while doing a tutorial at: http://www.iphonegametutorials.com/2010/09/23/cocos2d-game-tutorial-building-a-slide-image-game/.

The program I have typed out works except for the switching of tiles, and I have looked in the XCode debugger and it seems that my x and y values for the Tile class are being set way to absurdly high values. The weird thing is, when the values are passed to the method (initWithX:Y:) from the original method (initWithSize:imgSize:) they are what they should be, but when they arrive at the method they are huge (for example: in one instance an x passed as ‘1’ becomes ‘1065353216’ when it arrives at the method.)

I have a feeling that it may be pointing to the memory location of the passed int, but I don’t see any reason why it should be in my code. See below.

-(id)initWithSize:(CGSize)aSize imgSize:(int)aImgValue {
self = [super init];
imgValue = aImgValue;
size = aSize;
OutBorderTile = [[Tile alloc] initWithX:-1 Y:-1];
content = [NSMutableArray arrayWithCapacity:size.height];

readyToRemoveTiles = [NSMutableSet setWithCapacity:50];

for(int y = 0; y < size.height; y++) {
    NSMutableArray *rowContent = [NSMutableArray arrayWithCapacity:size.width];
    for (int x = 0; x < size.width; x++) {
        Tile *tile = [[Tile alloc] initWithX:x Y:y];
        [rowContent addObject:tile];
        [readyToRemoveTiles addObject:tile];
        [tile release];
    }
    [content addObject:rowContent];
    [content retain];
}
[readyToRemoveTiles retain];
return self;
}

-(id)initWithX:(int)posX Y:(int)posY {
self = [super init];
x = posX;
y = posY;
return self;
}

Everything should be the same as in the linked tutorial, but I can’t see anybody else complaining of the same problem.

I have also noted that if I go into the debugger and manually change the posX and posY values in the initWithX method that the tile switching code works, so my problem definitely lies with the really large int values forming in that method.

Edit for Jim: Hopefully this shows a more complete picture of the layout I have for the Tile object.

@interface Tile : NSObject {
int x, y, value;
CCSprite *sprite;
}

@property(nonatomic, readonly) int x, y;
@property(nonatomic) int value;
@property(nonatomic, retain) CCSprite *sprite;

@end

@implementation Tile

@synthesize x, y, value, sprite;

// Code is logged in below. 
-(id)initWithX:(int)posX Y:(int)posY {
self = [super init];
x = posX;
y = posY;
return self;
}

@end

Answer 1

Somewhere, the x and/or y value are being assigned to a pointer. One thing I would check is to make sure you aren’t declaring your ints as pointers to ints. I.e. int *x, etc.