May the Force Touch be with You

Sun, 19 Apr 2015 01:39:32 -0500

Last week I bought a newly updated 13" MacBook Pro with an amazing new Force Touch trackpad. I love it and it’s hard to go back to the older trackpad on my MacBook Pro at work. I’ve already caught myself trying to press on the top corners of the older version and have tried to press harder a few times. At this week’s NSCoder Night I decided to play around with the new Force Touch API to see how it works.

Apple’s site describing the APIs don’t really go into much detail about how to use them. However it’s pretty straightforward save a few oddities. Maybe they would be more expected had I been spending more time with AppKit.

I experimented with three different methods for detecting pressure with the new APIs. Responding to events on the responder chain and two different types of buttons added in 10.10.3. There are also new methods using NSGestureRecognizer and with Drag and Drop. The gesture recognizer seemed pretty easy and close to the events I was testing. I haven’t figured out the drag and drop capabilities yet.

Pressure in the Responder Chain

The easiest method seems to be to simply respond to the correct method

- (void)pressureChangeWithEvent:(NSEvent *)event;

in your application. Inspecting the NSEventTypePressure type event’s pressure, stage, and stageTransition allow you to determine the pressure across three stages (0, 1, 2). Looking at the pressure property to see the amount of pressure between 0.0 and 1.0. The stage property is aligned with the clicks you feel when pressing on the trackpad. 0 is the stage before the first click. 1 is the stage between the first and second click and, of course, 2 is the stage after the second click you feel. The stageTransition property describes the progress towards the next stage. When positive it is approaching the next stage, when negative it is approaching the previous stage.

Accelerator Buttons

Another way to detect pressure is using a normal NSButton with the new type Accelerator applied. These buttons will simply invoke their action repeatedly as pressure increases. For example, if you send the action from a button to

- (void)buttonPressed:(id)sender;

inspecting the doubleValue of the sender will tell you the pressure between 1.0 and 1.99. The action is called repeatedly until it reaches the end. It does not have any further clicks beyond the first click you feel. Here I bind the alpha value of a label to this value normalized to 0.0 and 1.0.

Multi-level Accelerator Buttons

The multi-level button is similar to the regular accelerator button above except you can specify how many levels, up to 5, the user feels when pressing the trackpad. With this type you are notified of the level the user has reached, not the actual pressure value. Inspecting doubleValue on this type of button responds with 1.0 to n where n is the value you set for the button’s maxAcceleratorLevel property. The really fun thing here is you feel an extra click in the track pad at each level here. This is likely how Apple implemented the fast forward feature in Quicktime Player. Pressing harder speeds up the fast forward feature across five levels. Here I bind a button to a progress indicator with a max of 5.

There are some other ways to take advantage of this new trackpad. Xcode will actually produce extra clicks when you are dragging UI elements around in Interface Builder. When the item you are dragging reaches a recommended constraint, you feel it. I haven’t quite figured out how to do this yet.

There is also this new concept for springLoaded that allows you to do specific pressure-sensitive behavior when dragging over a button.

It’s been a long time since I worked with AppKit, but I’ve been really wanting to get back into it and do something cool. These new gestures have me extremely excited about what I could build to support it.

I'm still working without a clock

Wed, 08 Aug 2012 22:23:32 -0500

Last year I wrote a post about how I was going to work without a clock. This was completely inspired by Cocoa developer Zach Waugh who wrote about the same topic. As part of this post, he also talked about his small Mac app called Clock.app which is an open source project. Since you sometimes need to know the time, the app provides a quick way to get the time using Alfred or Quicksilver to launch this simple app. For example, you can type cmd+space cl [enter] and I the time.

I actually stopped doing this for awhile. I’m not sure why. I love working this way and recently went back to the clock-free environment. It works so well for me that when I’m working on an app on my phone and see the time, I get a little upset.

One small problem I had was I often used the clock to identify the date. Since it was open source, I forked it and updated Clock.app to have the date.

If you’d like to try it out, you can download the built version from Github or checkout the source.

Global hotkeys in Cocoa on Snow Leopard

Fri, 23 Jul 2010 01:44:32 -0500

I am working on a small app at the office for all our mac users to help locate files on the network (more on this later), I decided to go with a spotlight style NSStatusItem based app. I’ve been really inspired by these apps lately (when done right). Mostly thanks to Notify.

To make this more handy I decided to include a global hotkey. For Leopard and earlier, one problem is you have to use the old Carbon-based events. Most likely due to my Carbon-naivety, I had troubles with this.

Luckily, I found that starting with OS X Snow Leopard, Apple added a new method to NSEvent: