Add support for building separate apps; SpriteGame example #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Including translating errors to Swift exceptions
The App is now back to being a class, so it can create a closure that updates its state. That probably makes more sense anyway
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switched to SPM for builds, with a legitimate
swift-pd/Playdatepackage you can include as a dependency in a separate package.Still using a dumb bash script for builds, but at least I can now include more than a single trivial example.
Ported the example C game "SpriteGame", along with the Bitmap, Sprite, and input APIs it required. That was fairly involved and turned up a lot of fun issues with refcounting, capturing closures vs C function pointers, and so on. Anyway a lot of stuff is there now so the next app should port more easily.