Some how Xcode’s “Attach to Process by PID or Name..” came up recently in conversation and several of my developer friends had never heard about it. I’d like to quickly walk through my favorite use case, auto attaching to a process when it launches.
UIKit has a built in physics engine called UIKit Dynamics. It’s how Apple has implemented quite a few of the animations in iOS. It’s pretty powerful but it can also be a pain in the ass to debug. According to Session 229 from WWDC 2015, the supported way for debugging is to use private API on UIDynamicAnimator. There are some hacks for gaining access to private API inside of Objective-C — things like using NSInvocation — but they’re not supported in Swift. That’s ok though, because Apple actually wants us to use lldb to access this private API.
Just a quick heads up, since this just bit me again.
TLDR: Please help me raise money and consciousness for men’s health awareness. Please donate here: http://mobro.co/averagejake
I was recently asked to speak at Starbucks for an internal thing they call Tech Talks. It was a great crowd and lots of fun. I gave a talk about adding Swift into an existing Objective-C application and framework. This post is mostly to share my slides and code.
Here are the slides for the Xcoders talk I just gave on LLDB Python Scripting. I’ll update this post when the video is uploaded.
As the title suggests, this is a followup to my previous post about Custom Presentation Controllers and Adaptability. In that post I argued that the current API for custom presentation controllers is a little lacking when it comes to switching between custom and system provided presentations during the life of a single presentation. A friend of mine proposed a workaround that I’d like to explore. Feel free to grab the code and follow along: CustomAdaptablePresentation
Last year, with iOS 8, Apple gave us the ability to customize view controller presentations. Not only can you create a custom transition for a presentation, you can now add behavior to deal with adaptability. Recently I hit a wall with using a custom UIPresentationController.
First things first. UIBarButtonItems are not views. They’re more akin to model level objects. You create them and set up styling on them, but the framework converts their properties into actual UIView subclasses. And this is were the majority of problems that I have with UIBarButtonItem come from.
I’ve already written about Adaptability a bit, but iOS 8.3 was released today and with it we got a few new additions.