> > Note that if you select the AirPort item in the first pane, the action > will automatically be On or Off depending on the current state.
I also noticed this behavior in the Triggers pane when trying to make a trigger with the Airport actions (you have to toggle the AirPort to make the opposite one). Why do these actions not generate Growl notifications when the interface goes up or down? I see none from Hardware Growler which I have installed, but this is probably related to how it works. On Monday, April 23, 2012 2:59:47 PM UTC+2, Rob McBroom wrote: > > On Apr 22, 2012, at 11:52 PM, CakeFace wrote: > > > try saving the following applescript as an application, and then making > a trigger to launch it. > > I used to use that AppleScript. I updated the plug-in so I wouldn’t have > to any more. The next version of the plug-in will offer some way to assign > a trigger for toggling (without stepping in AppleScript), but let me go on > the record as believing this is silly. :-) > > Note that if you select the AirPort item in the first pane, the action > will automatically be On or Off depending on the current state. So the > default action should always toggle to the opposite state without you > having to pick anything. On my system, Quicksilver is trained to the point > that just typing ‘A’ finds the AirPort item. > > So in the end, all I have to do is ⌘Space, A, ↩. Is it a trigger? No. But > it’s plenty fast (and saves me the headache of finding a globally unused > keystroke and then remembering what it is). > > -- > Rob McBroom > <http://www.skurfer.com/> > >
