Search code examples
ios7sprite-kitjstilemap

JSTileMap generating warnings in ios7 SpriteKit template

I am copying JSTileMap and LFCGzipUtility into the project and when I run the application it generates several warnings for both files.

However, when I run the provided sample from github, I don't see any of those warnings.

I would like to know why is there a difference, and in case, what am I doing wrong?

For reference please visit, https://github.com/slycrel/JSTileMap

Clarification, I would like to know if there is anything I should change in the project settings, rather than debug the code that runs just fine and without any warnings on the provided sample at the links above.

Solution

  • if you are running your app in the iOS simulator 64 bit mode then the problem is that the files of JSTileMap are not updated to 64 bit architecture

    Apple documents says

    Code that relies on the NSInteger and CGFloat types needs to be carefully examined.

    Start by building the app for the 64-bit runtime, fixing any warnings that occur as well as searching your code for specific 64-bit issues. For example:

    Make sure all function calls have a proper prototype. Avoid truncating 64-bit values by accidentally assigning them to a 32-bit data type. Ensure that calculations are performed correctly in the 64-bit version of your app. Create data structures whose layouts are identical in the 32-bit and 64-bit versions of your app (such as when you write a data file to iCloud).

    here is the Apple's transition guide to 64 bit:

    https://developer.apple.com/library/ios/documentation/General/Conceptual/CocoaTouch64BitGuide/Introduction/Introduction.html

    if that is not your case the open the file JSTileMap.m, inside press command + f type warning and press enter

    and you will find all the warnings that JSTileMap want you to see just comment all warning and thats it

    Here i show you all the warnings

    #warning these appear to be incorrect for iso maps when used for tile objects!  Unsure why the math is different between objects and regular tiles.

#warning This needs to be optimized into tilemap layers like our regular layers above for performance reasons.

#warning the positioning is off here, seems to be bottom-left instead of top-left.

#warning need to write setTileGidAt:

    Good Luck!!