bradengammon

Have you had any luck with modifying the theme URL itself and then importing it?

I also feel like the functionality of v1 might be a bit too compressed into the Workflows tab in v2. The hotkey functionality definitely still exists, but it is definitely not as intuitive finding it. You have quite a bit of window bar real estate to play around with, so maybe separating the workflow functionality back out into multiple tabs would be a good idea.

I see what you are saying about slowing Alfred down. Thanks for the idea. I don't know if it would do much to help my situation. If there is no QuickTime document, then the second script won't have any effect anyway. It's relying mostly on the application's default behavior, so I'm not really concerned. I am completely new to AppleScript however, so is there a way that I can prevent the notification output from appearing if the second AppleScript were to return false or something like that? Thanks

I wanted to make a workflow that would easily allow me to make screen capture videos with QuickTime Player. I set up a workflow containing two "Keyword to AppleScript to Notification" 1) has keyword "screencast" that runs the following AppleScript on alfred_script(q) tell application "QuickTime Player" activate start new screen recording end tell tell application "Finder" to set visible of process "QuickTime Player" to false end alfred_script then outputs a notification that says "Recording..." 2) has keyword "stop" that runs the following AppleScript on alfred_script(q) tell application "QuickTime Player" to stop document "screen recording" end alfred_script then outputs a notification that says "Finished recording." I want to be able to associate those two keywords, where the second keyword "stop" requires the first keyword "screencast" to have been used first. Typing "stop" into the Alfred window would not display a result unless "screencast" had been used first.