You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
You’d normally want to draw in response to a CVDisplayLink callback (which MTKView uses internally on macOS), but you can also use the setNeedsDisplay/updateLayer mechanism to provoke drawing into a CAMetalLayer. Happy to discuss further on DM.
As you observe, Cocoa generally wants to be event-driven, so you wouldn’t want to redraw in a tight loop because (1) you’ll starve the runloop event processing mechanism and (2) you’re going to wind up blocking in -[CAMetalLayer nextDrawable] if you try to run too far ahead.
Right! I suspected I needed to go event driven somehow. But how do you usually implement a game loop with that? Trigger a new request for a draw when the last one finishes?
Perhaps. There are of course many, many ways to tackle synchronization, but in the simplest case, you’d run a CVDisplayLink at your target frame rate and kick off rendering from the callback.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
