FYI - I wasn't able to find your app on my nexus when searching for "math machine". I found it only when looked for "woodencloset". As for the app - great idea and nice implementation, but for someone who understands…
To my understanding - yes, all "assets" are typically included. In most of the cases though, all assets (textures, geometry, sounds, camera paths) are generated during runtime. More information can be found, for example…
A couple more interesting swift features that seemed a bit weird to me after skipping through the reference: 1. Strings, arrays and dictionaries are value types (like structs in C# - stored on stack, not on the heap)…
Are you sure this should work? I checked the grammar once more and it seems that closure-expression should always be enclosed in { ... }
I don't have XCode to try it out, but according to the book, you can replace var spawn = SKAction.runBlock({() in self.spawnPipes()}) with var spawn = SKAction.runBlock({self.spawnPipes()}) or even var spawn =…
FYI - I wasn't able to find your app on my nexus when searching for "math machine". I found it only when looked for "woodencloset". As for the app - great idea and nice implementation, but for someone who understands…
To my understanding - yes, all "assets" are typically included. In most of the cases though, all assets (textures, geometry, sounds, camera paths) are generated during runtime. More information can be found, for example…
A couple more interesting swift features that seemed a bit weird to me after skipping through the reference: 1. Strings, arrays and dictionaries are value types (like structs in C# - stored on stack, not on the heap)…
Are you sure this should work? I checked the grammar once more and it seems that closure-expression should always be enclosed in { ... }
I don't have XCode to try it out, but according to the book, you can replace var spawn = SKAction.runBlock({() in self.spawnPipes()}) with var spawn = SKAction.runBlock({self.spawnPipes()}) or even var spawn =…