Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/02/2021 in all areas

  1. While I'm at it... here is another feature request for the Universal Actions! It would be great to be able to programmatically run a Universal Action, I mean, without popping the actions list. This way, we could create hotkeys that directly trig an action. One example, one file action that I'm using a lot is the "Open with..." and I think it would be great to be able to assign a hotkey that would directly activate this action so I would directly get the list of applications to open the file with instead of needing to select the action first (or doing it with a script that automates typing). The way I'm thinking of implementing it would be to add a "directly run action" parameter inside the "Action in Alfred" workflow action and where we could get the list of available actions from a drop-down menu. In short, like the "Workflow Triggers" button inside the "Call External" object. With that, it is already possible to connect another object after the "Action in Alfred". However it is run directly when the UI pop at the moment. I think it could be an option to make it blocks until the user has selected an action so we can run something after sequentially (maybe having a parameter to specify if we want to run in parallel or sequentially would be useful). This way (and with the possibility to directly run an action) we could chain multiple actions together to make it easy to build workflows with small parts from different workflows and that chain together in the order that we want. I mean, we could do something like: User select a piece of text then run a workflow that do [ "Action: Extract URLs from Text..." > "Run Script: That filter to a specific kind of URL" > "Action: Save as Snippet" ] This could be used as an alternative to the "Call External" object, but where the workflow that is called doesn't need to know the caller and calling it with a specific "Call External" object to return the result since the "Action in Alfred" object will encapsulate the input and output of the workflow.
    1 point
  2. This would be a big help, imo. "Text" is extremely broad as types go. It would be nice to be able to have very specific actions (e.g. one that parses and processes tasks actioned in Things.app) only available at very specific times. It would also be handy if Alfred didn't reset the clipboard immediately after grabbing the selection: it throws a lot of useful information away. For example, when you copy a link in many applications, they put the title as well as the URL on the clipboard. Alfred doesn't just ignore that info itself, it actively purges it. I think Universal Actions would be a lot more universal if Alfred left that door to getting a richer representation of the selected data open. Perhaps Alfred could only reset the clipboard after the workflow has completed (without altering the clipboard itself)?
    1 point
  3. My mistake on the upload, I uploaded your version! I’ve updated the link with the correct Workflow. Note that it no longer requires quotes, you should just m 5 foo bar or ./test 5 foo bar and it will divide it into the first argument (SCALE) and everything else (DESCRIPTION).
    1 point
×
×
  • Create New...