Supporting the Pencil
I'm happy to finally be able to share what I've been working on: supporting the Apple Pencil.
In this post I want to cover the basics of supporting
UITouchType.Stylus, some conveniences to make it easier to support iOS 8 and iOS 9.0, and a hole in the current processing of events in iOS that can make supporting the Pencil tricky (plus . . .
Leaks is a filthy liar
This is a blog post I started many months ago and never got around to finishing; please forgive any outdated screenshots or references. The core ideas are still relevant so I'm gonna go ahead and post it. The bug in UIKit that confused Leaks into missing the cycle was supposedly fixed but a good Software Engineer should . . .
A small detour
In Xcode 7 Clang learned a new trick: Objective-C generics. Now that I've started using this feature in our legacy code I can't live without it. Even without Swift interop consequences I would still use it.
Objective-C can now declare that an
NSArray is an
NSArray<NSString *>. This helps on the Objective-C side by . . .
Another day, another Xcode beta.
IDE & Playgrounds
- You can now set Swift Error breakpoints, including restricting the breakpoint to specific error types.
- The in-playground API has been revamped.
XCPlaygroundPage.currentPagenow grants a reference to the current page.
- The playground live view support has been enhanced. Types can adopt
. . .
If you thought Apple was slowing down with Swift, think again. Xcode 7.1 Beta 2 includes Swift 2.1. As always you can check the release notes for yourself because I don't necessarily address everything here.
Interop & Types
- Enums imported from C automatically conform to
Equatableso now they work in pattern matching switch statements . . .
Some highlights from Beta 6:
Compiler & Tools
- A new
try?keyword has been added. This attempts an operation that may throw (fail). If it succeeds the result is wrapped in an optional. If it fails the error is ignored and
nilis returned. This seems like a pragmatic compromise but I have to imagine someone lost a battle somewhere because . . .
Way too meta
What about Swift? If you've looked closely at the Swift Language Reference you'll see two short paragraphs describing
SomeClass.Type, a short example (that doesn't address
Type at all), and that's it.
In Swift, all types have metatypes, not . . .