![]() With that, what I've been thinking that would be great is to add an option to the Universal Action trigger to make it active or not only in specific applications. I know we can add the Universal Action trigger inside a workflow for that, but I'm wondering how we could disable/activate it when imported from a downloaded workflow (actually, this is something that I think would be great to add to every workflow objects: being able to disable/bypass it so we could tidy our list of actions that appears in Alfred) With that, in the Universal Actions preference, instead of having toggles, it could be a drop-down menu for those 2 types (Keywords + Script Filters) to specify if we want "all of them", "manually activated inside workflows" or "none". So, what I'm thinking is maybe it could be great to add an option to the Keyword and Script Filters objects to specify if we want it to appear in the Universal Actions list or not. However, I think it would be great to be able to configure it more than to set it to all or nothing since there's some workflow I could benefit having there. I also found that with the "Workflow Keyword Inputs" and "Workflow Script Filters" ticked I have a very long list of actions, so I unchecked them at the moment and find it better. To get back to yes maybe some extra usability options could be great. I don't know if you are trying to build something in this regards during the last days, but if so I'm sure it's going to be great and if not then I'm good with my setup! So, I would say that I'm good with my request It would be great to make it faster to have it natively inside Alfred, but I think the workflow object makes it customizable quite well. Right now, I set a condition that if there's no input then I run my script to try to get the file or the URL from the front application and then pop the Universal Actions with the found value or run another workflow if there's still nothing found. With that said, thanks for this new feature! It is already really great how it is and seems to work great at the moment by playing with it a bit!įrom everyone replies, I think we all always want more, I had a play on my side and actually I'm able to get what I want (with the pre-processing of the input) by calling the Universal Actions from a workflow triggered by a Hotkey (so, like I did before, but now I can get a universal actions list instead of a specific workflow when actioned with a string). I'm not sure if I'm completely clear, so please let me know if I’m not explaining it well! I think I would prefer to have a specific parameter for the fallback action since now I find it greats that we can "disable" the trigger by unchecking all the toggles (I'm thinking regarding when installing a downloaded workflow where I would disable this universal action on my side). This could work as some kind of fallback actions, but this would be different than having an action list when nothing is selected as I said in the above paragraph. So, I think it would be less confusing to remove the word "only" from this sentence (maybe just for myself ) or to make it act like the action will appear in all the types. I mean, it says: "Only show this trigger when the input argument match the type.", so I was thinking that if nothing was selected from the toggles above then it would be listed all the time since the input wouldn't match "only" the any of those types. ![]() ![]() On my side I would even like to have a "pre-process" script that could be run so I can see if I can automatically run a specific script and if it doesn't get any results then it would pop the fallback actions list.Īctually, by reading the text in the "Universal Action" trigger, I got the impression I could get an action that would be in the list all the time. With this new feature, I can get the first 2 actions, but what about when nothing is selected? I understand this is maybe a bit counterintuitive, but I think it would be great to have a "fallback actions" list that would pop when nothing is selected so we could add some pre-defined actions that could be invoked to run a specific script in those circumstances. Great new feature! Actually, I did a workflow that does that a long time a long ago that replaced the File Action with a custom Hotkey action that would detect if a file was selected or simply text or nothing and invoke the File Action or a custom workflow that give me a list of text processing actions or a custom script that would try to get the opened file from the front window if nothing was selected and then pop the File Action on the file that the script found.
0 Comments
Leave a Reply. |