Hacking AirClick USB (for Mac): Part Deux

Hello AirClickers! Or is that AirClickUSBers? Anyway, with the new release of the AirClickUSB software come a couple of changes to the way things work.

Pretty much everything that I mentioned in the first entry about Hacking the AirClick USB still applies but there were a few changes to organization. First, all the scripts are now found in AirClick/Contents/Resources/scripts. Next, you’ll notice that all of the AppleScripts end in .applescript instead of .scpt. Getting text AppleScript files to end in .scpt was tripping up a lot of folks and for the life of me I’m not sure why the .scpt extension was being used in the first place.

The other changes were additions to the functions.plist file. A function definition may include the ShowInMenu key, with a Boolean value set to Yes, to display the Name of the function in the reference submenu. Unfortunately, the AirClick software only displays the primary button used to trigger a function. There’s just not a practical method to indicate things like a function that is triggered after play is held for 5 seconds with the volume up key modifier if the variable WTF is set to 3.

Finally, the AppBundle key was added at the function group level. Use this to associate a group of functions with an particular application indicated by it’s bundle identifier, ex. com.apple.iTunes. Right now this is only used to find an icon to display when changing the selected app from the AirClick remote (Volume Up/Down while holding the Play button).

With the next release, we’re thinking about adding a mode that tells the AirClick software to control the active application if it can, and if not then fall back to the application selected in the AirClick menu. The UTI described by the AppBundle key will used to make the determination as to whether the active application is controllable.