ctwise Posted January 29, 2013 Share Posted January 29, 2013 It would be nice to be able to generate a list of context items for results of script filters. Link to comment Share on other sites More sharing options...
jdfwarrior Posted January 30, 2013 Share Posted January 30, 2013 This has been requested already by multiple people. As mentioned in the other threads, this isn't currently available because of the ability to customize script filters to have any kind of output. Current result actions are available because the result types are known. They are a file, or a contact, etc. With script filters, it could be any kind of generic text. Maybe something like this could be added in the future but it would probably require the additional ability to create custom result actions for a workflow. So, long story short, it can't be done right now. Link to comment Share on other sites More sharing options...
CarlosNZ Posted January 30, 2013 Share Posted January 30, 2013 What you can do (I've just done it in a new workflow) is use Applescript to load the chosen item back into Alfred's text field. It's not perfect, but it's a pretty good stopgap solution: tell application "Alfred 2" to search "{query}" Link to comment Share on other sites More sharing options...
deanishe Posted February 3, 2014 Share Posted February 3, 2014 This has been requested already by multiple people. As mentioned in the other threads, this isn't currently available because of the ability to customize script filters to have any kind of output. Current result actions are available because the result types are known. They are a file, or a contact, etc. With script filters, it could be any kind of generic text. Maybe something like this could be added in the future but it would probably require the additional ability to create custom result actions for a workflow. So, long story short, it can't be done right now. However, there's no reason why Alfred couldn't allow workflows to output <action> items as well as <item>, err, items. That way, workflows could provide custom actions for their own items. Alfred need know nothing about the nature of the items, just pass along their respective args to the workflow-specified actions. That would allow workflows that work with very different data types to integrate seamlessly with Alfred, even if Alfred doesn't understand the data they're using at all. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now