on launchers and other nerdy things
¶ by Rob FrieselTerribly interesting finding in my main console.log file today…
May 24 08:38:07 KetelOne /Applications/Quicksilver.app/ Contents/MacOS/Quicksilver: LaunchApplication (/Applications/Utilities/Terminal.app) May 24 08:38:10 KetelOne /Applications/Quicksilver.app/ Contents/MacOS/Quicksilver: LaunchApplication (/Applications/Firefox.app) May 24 08:38:14 KetelOne /Applications/Quicksilver.app/ Contents/MacOS/Quicksilver: LaunchApplication (/Applications/Mail.app) May 24 08:38:20 KetelOne /Applications/Quicksilver.app/ Contents/MacOS/Quicksilver: LaunchApplication (/Applications/iCal.app) May 24 08:38:43 KetelOne /Applications/Quicksilver.app/ Contents/MacOS/Quicksilver: LaunchApplication (/Applications/Microsoft Office X/Microsoft Excel) May 24 08:38:46 KetelOne /Applications/Microsoft Office X/ Microsoft Excel: *** Warning: ATSUMeasureText has been deprecated. Use ATSUGetUnjustifiedBounds instead. *** May 24 08:39:14 KetelOne /Applications/Quicksilver.app/ Contents/MacOS/Quicksilver: LaunchApplication (/Users/rob/Applications/VoodooPad Lite.app)
Now, I know that these apps launch in this order from an AppleScript that I run when I plug in at work. The interesting thing (to me) is that the console is suggesting that these apps were launched by Quicksilver and not by the AppleScript that queues them or even Script Editor.app. So the mystery becomes: How is Quicksilver owning these launches? Especially since Quick silver isn’t even invoked in the script… Just plain ol’:
tell application “Terminal”
activate
set the bounds of window 1 to {20, 20, 820, 620}
end tell
tell application “Firefox”
activate
end tell
And so on…
Leave a Reply