Caching?
Spent at huge part of the hour today troubleshooting why my API change to an init method was not being seen by the playground. Weird caching bugs? No; it turns out that XCode was building for target instead of simulator, so the playground didn’t get a rebuilt version of the framework when I hit build. Still don’t know why that changed since last time, but oh well.
After that frustration was cleared I proceeded to learn that Swift has the same semi-dynamic Array notion as Objective C has, so they need to be properly managed with respect to reserving space and inserting new objects.
Next related
Directional Navigation
Prereq work for implementing path finding: eight direction navigation. A tile can find its neighbours within its layer exit(direction:). Currently only within a single map region, because we haven’t implemented interregion links yet.
Previous related
Swift First Lesson
The first lesson turns out to be about access control: nothing is public by default, even classes or their init methods. With public access to our classes the playground plays.
Travel Double Day
This fell apart quickly, as expected, with a friday that began in CET and ends about now in EST, with 12 hours of air travel and such in between. But development evnvironment is now setup on laptop as well, so at least there’s hope for the following days.
Second of Devember
Trying to sketch some basic structure for possibly hierarchical map definition, and trying (failing) to use a Swift Playground to try the framework code while sketching. The playground can import my framework, but the framework classes are not accessible for some reason. That’s all I got from one hour today.