Btw, I found this script /Library/Scripts/Networking Scripts/Toggle AirPort.scpt. It has been mentioned here a while ago and has been updated in the meantime. You can get it at https://github.com/andrewheiss/AirPort-Toggle It registers for Growl notifications.
Sometimes I need a quick shut/no shut of the AirPort connection, mostly when it lags for no apparent reason. For this I just saved a trigger to run -- Quickly Shut Airport Power On and Off *do shell script* "networksetup -setairportpower en1 off;networksetup -setairportpower en1 on" On Tuesday, April 24, 2012 3:17:49 AM UTC+2, Patrick wrote: > > > > Rob, what do you think of implementing Growl for triggers? > > > Generally, it seems like a good idea. What we’d more likely do is add a > “Show notifications” option and then individual users would be able to > specify whether those use Growl or Quicksilver’s built-in notifications. > > I really like the idea, and will try and get it implemented for one of the > upcoming releases. As Rob says, altering the option to 'show notification' > and using the default notification handler would most likely be the best > option > > On 23 April 2012 18:57, Rob McBroom <[email protected]> wrote: > >> On Apr 23, 2012, at 11:02 AM, su wrote: >> >> > Rob, what do you think of implementing Growl for triggers? >> >> Generally, it seems like a good idea. What we’d more likely do is add a >> “Show notifications” option and then individual users would be able to >> specify whether those use Growl or Quicksilver’s built-in notifications. >> >> -- >> Rob McBroom >> <http://www.skurfer.com/> >> >> >
