vitor

@Stephen_C Great catch. I didn’t even remember I made that.

Connect a Keyword Input to a Folder Contents Automation Task, then to a Grid View. Or use the Fast Entry Configuration option in Thumbnail Navigation. If you really want it as a list, that’s also doable. This workflow has both options. The notes on the objects tell you what you need to edit. See the Getting Started Guide for an interactive tutorial on making a workflow. There is comprehensive documentation on the website to follow up (tip: find help for any object fast by clicking the (?) icon while editing). You may also be interested in the YouTube channel or the Simple Ideas series of forum posts.

You have to enable permissions to record the screen.

@Octavius The best way is to follow the instructions at the bottom of the post on April 1.

Welcome @gogamid, Couple of tips for the workflow: Workflow icons should generally be 256 x 256 px or higher.Always prefer with input as argv over with input as {query} (relevant for the Run Script).This seems like it needs a specific app and it’s command-line too in PATH. It would be useful to let users know how to get that, particularly the common-line tool.

Those dependencies are recorded on the Gallery’s side, they work for Gallery workflows.

Only by signing and notarising them, which requires an Apple Developer Account. Not having one, using the Run Script with Swift as the language saves a ton of headaches for users.

When you first take a screenshot with the Automation Task, macOS asks if you want to give Alfred permission to record the screen. This is unavoidable, the Automation Task uses Apple’s own screencapture tool. If you refuse the permission, only the Desktop is saved in screenshots. Go to System Settings → Privacy & Security → Screen & System Audio Recording, and enable Alfred there.

By using unsigned non-notarised binaries, it won’t run on most user’s machines without some work (and warnings from macOS). Have you considered using Run Script Actions with the language set to /usr/bin/swift? That way the code is compiled at usage time.

Editing the plist should indeed work, I have just tested. Make sure that section looks like this: <key>hotkey</key> <integer>12</integer> <key>hotmod</key> <integer>1048576</integer> <key>hotstring</key> <string>Q</string> Or try this quick example. Naturally, all the caveats apply that replacing ⌘Q could lead to undesirable results as far as macOS is concerned, so be careful with that.

@luckman212 Same answer applies. If you’re not using it, you won’t notice it. Efficiency and low resource usage are way up on the list of Alfred priorities.

The External Trigger shows you the syntax.

That’s basically running both shortcuts in a row: ⌘⌥H and ⌘⌥M. Make two successive Dispatch Key Combos.

Welcome @mcgaritydotme, Just added the feature. It required more changes than initially predicted as I tried some different solutions, so it should still be considered experimental. Give it a try in this preview version and if everything works well I’ll release it.

@blgentry The current version of the workflow always uses the Python version from macOS, not Homebrew. If you’re having that problem, you’re likely not on the latest version on the workflow.