Floating.Point

Hello, it would be really nice if the Text View node allowed a custom CSS file to be loaded - so we can style different Text View outputs in different ways.
Thanks for considering this feature – Nathan

These are fabulous! These will help me show friends why Alfred is such a must-have for their day 💖 

I've just published our first two videos about Alfred on YouTube
 
You can find our videos at https://www.youtube.com/@alfredapptv
 
Making the time to create more videos about Alfred is exciting, and we'd love your help getting the word out. Share, give it a like, all that good stuff! Thanks for being the best community on the internet!
 
You can see the ChatGPT / DALL-E workflow in action here:
 
 
 
And another on using and setting your fallback searches:
 

The text view uses a native macOS Scroller for the text view, so you won't get the themed scroller like in Alfred's default results. You're seeing it like this because you likely have your macOS setting to "Show Scroll Bars: Always". If you set this to the default of "When Scrolling", you won't get the background drawn behind the scroller.
 
Having said that, there are a few things you can do to make this look a little better if you want to keep the macOS "Always" setting enabled.
 
1. Assuming macOS is in dark mode, Switch Alfred's dark mode rendering to native in the Appearance > Options > Use Native Dark Mode window rendering... This should make the background darker and fit with your theme better.
 
2. Update the theme to use a Visual Effects View background. You'll lose the pink border, but this uses a more modern window content view, and the scrollers are rendered differently.
 
Let me know how you get on
 
Cheers,
Andrew

Updated to 2024.1.
Skip Input as Universal Action. Remove colons in keyboard shortcuts. Edit shortcut with Automation Task. Add Hotkey. Use JSON caching. Split between shortcuts which take input or not. Convert scd to JXA. Shorter Objective-C functions. Fix typo.

@Andrew Yep confirmed fixed 👍

@Floating.Point The original reported issue should now be fixed in 5.1.3 b2175, could you let me know?

I thought this workflow might be useful to some (for sure it's a small group!) - so posting it here.
 
It copies a "deeplink" to a specific workflow object, which is a link that uses the alfredpreferences:// URI scheme to open the Workflow Editor directly to a specific Workflow, with a specific Object highlighted. This might be useful to developers, or anyone really, for keeping notes or internal documentation about specific Workflows you're working on.
 
See README for details on how to use...
 
Requires Python3 + Alfred 5.1+
 
https://github.com/luckman212/alfred-get-deeplink-to-objec

Howdy Vitor,
 
Firstly thank you for this insanely helpful workflow. Such a superpower to add to Alfred! (Another superpower! 🦸‍♂️)
 
I assume the limitations preventing access to minimising windows might be the reason this isn't possible, but couldn't hurt to ask…
 
Is there any change this could be configured to find all open apps (even on different spaces?) or even those that are fullscreen?
 
Cheers, Nathan

You may want to have a look at the "rerun" key.
 
 
On the first run, return the results that are loaded quickly, immediately rerun, then execute the slow script and return the results. If the Alfred window is still open, the first results will be replaced. (You could pass a variable that acts as a token to indicate that the slow script should be run now).

Thank you for being understanding and explaining your use cases thoroughly. It’s especially rewarding to help those who help themselves and have a clear desire to do things well.

Ah yeah I don’t want to do anything hacky. I think I have always just incorrectly assumed ‘always’ mode would show a scroll bar even when there was nothing to scroll. Don’t I feel foolish now, learning this is not the case. Changing from ‘automatic’ mode to ‘always’ mode is all I needed to do. I assume this is Alfred’s default too and I must have just changed it years ago and never thought twice about it. Thanks for humouring me and as always being so gracious and helpful 😊

Ah lovely, this is great news! This functionality isn't at all critical, but it's a nice addition. I will proceed, but stay mindful of future breaking changes. Thanks Vitor 🙏

Things to take into consideration: due to caching, you may still see the previous icon on occasion; and you’re changing the icon in the workflow itself so when you share it you may be doing so with one of the modified icons. None of those seems like a deal breaker for your use case, though. Your specific mention of the ID changing shouldn’t be a worry.
 
Just keep in mind that what you’re doing isn’t officially supported so don’t rely on it for anything critical. But if there’s anything in the future which changes that behaviour, you’ll probably be able to see it in Alfred’s release notes.

Usually I’d be all for submitting such Feedback to Apple, and I’d even have a number you could duplicate in Feedback Assistant, but I doubt in this case it’s going to make a difference because Apple’s own tools work like that: In the Shortcuts app, add a “Find Windows” and tell it to find “All Windows”. Then run the Shortcut. You’ll only see the windows in the current Desktop too. But if you still want to open a report, you can mention the “Quartz Window Services”.
 
Unrelated to that, just pushed a new release (2023.5) which changes how unnamed windows are presented (now it’s the name of the app instead of “Unnamed”).

Usage

Generate a backup of your local Alfred Preferences via the start backup keyword. A macOS launchd agent will be loaded to do it daily at the time set in the Workflow’s Configuration (using the 24-hour clock format). The number of versions to keep is likewise configurable.



Restore a previous version with the restore backup keyword. It takes a few seconds to complete and restarts Alfred.



⤓ Install on the Alfred Gallery | Source

No worries at all, thank you for the handy workflow!

if you don't mind creating and maintaining a list filter with all the object names and keywords, you can do the following:
for each of the 'tools' you want to launch, right click to set an external identifier in 'Inbound Configuration...' create a Call External Trigger object. Use the trigger Id of any of the 'tools' in your Workflow you set in #1 right click on the Call External Trigger object and select 'Copy Configuration'  create a JSON config object replace the JSON text with your clipboard (which should have the 'Copy Configuration' string you copied earlier) within the new JSON text, replace the tool name you selected in #2 with {query} connect your list filter (which will have the keyword as Titles and all the object names as arguments) to the JSON config object connect the JSON config object to the Call External Trigger object, like this:
 
Now, actioning one of the keywords from the list filter will launch the corresponding 'tool'. 
Next, if you want to generate the list filter automatically from the info.plist file, this can be done with a Python script. 
 
I hope this makes sense! Let us know if you run into trouble.
 

The way to go is (almost) always to ship the dependency with the workflow. Pillow is so far the exception because it has unsigned binaries which cannot be removed. But telling users to run the pip command themselves is to be avoided. However, Pillow is available in Homebrew so it can be added as a dependency in the Gallery that way, that’s the way to go. @BenjaminO will be the best person to help you there; Emoji Wine uses that solution.

The configuration JSON from an object is not the same as the JSON interpreted from a Script Filter (see docs).

Seeing as you’re reading an environment variable, that also needs to be taken into account. Try this:
 
// Correct path between the quotes const filePath = $("~/Documents/Notes/Databases/References/Metadata/Tag List.md").stringByExpandingTildeInPath.js // Leave unchanged from here const theTags = $.NSProcessInfo.processInfo.environment.objectForKey("displayTags").js const fileData = $.NSFileManager.defaultManager.contentsAtPath(filePath) const fileContents = $.NSString.alloc.initWithDataEncoding(fileData, $.NSUTF8StringEncoding).js const topItem = [{ title: "Finished tagging", arg: "Done", subtitle: theTags }] const sfItems = fileContents.split("\n").map(item => ({ title: item, arg: item })) JSON.stringify({ items: topItem.concat(sfItems) })  

Checking for an extension isn’t reliable because files can be extensionless. @Stephen_C’s solution is clever and should work, but I’ll add proper checks for “Is File?” and “Is Folder?” for the next Automation Tasks release.
 
In the meantime, you can use a Run Script with default settings and code: [[ -d "${1}" ]] && echo -n 'true' || echo -n 'false'. That will be true if a folder and false if not.
 

Cautiously optimistic about it being fixed. It’s still broken on the current Ventura release (13.5, released on the 24th) but appears to have been fixed on the current Sonoma beta (4, released on the 25th). Hopefully the fix will be retrofitted to the next Ventura release.
 

It’s not user error, it’s Apple error. The regression is in Shortcuts itself in a recent version of Ventura. We’re aware and it’s already been reported to Apple. Ostensibly Apple gives priority to bugs with multiple reports, so if you’d like to help bump that up create a report with Feedback Assistant with the name Regression: "Shortcuts Events" fails on list of files and in the body mention you’re duplicating FB12163725.
 
It’s not even the only broken feature Shortcuts has, unfortunately. The shortcut has already needed to change once before due to it.

Hi, @Mr Pennyworth It's really a shame that one of the greatest Alfred workflows such as yours is no longer being monitored.
 
I've posted an issue on the GitHub repository notifying you about the common issue where Displaying a message on macOS Ventura using Alfred 5.0.5 saying:
"This workflow uses an Alfred feature only available in v4.3.0 and newer. The installed Alfred version is v0.0.0."
 

 
Would anyone have any suggestions on how to fix it?

Unfortunately the PR hasn’t been merged yet, so moving to closed for now. UTF Search in the Gallery works well.
 
Don’t be discouraged regarding the PR, though! It sometimes happens that the maintainer of a project can’t get to them, it definitely should not stop you from submitting others.