vitor Posted August 5, 2019 Share Posted August 5, 2019 The “Don’t close the Alfred window on actioning result” Window Behaviour option choice is always a hard one for me. I have multiple nodes in multiple Workflow where I want both behaviours at different times. One way to achieve this is to add a new connection with a modifier that performs the opposite behaviour. This is hacky at best, and needs to be added manually each time to each specific option. My suggestion is a new behaviour with a global shortcut. Let’s say we’re on a result window that typically closes when picking a result. We double press ⌘ (or any other shortcut) and get a small padlock on the top right (I’ve used icons from my Workflows because I had them on hand). The window will stay in the “Don’t close the Alfred window on actioning result” mode until we dismiss it, at which point everything goes back to normal. deanishe and dfay 2 Link to comment Share on other sites More sharing options...
deanishe Posted August 5, 2019 Share Posted August 5, 2019 This would solve some of the issues I have with “External Trigger mode” and its incompatibility with Alfred’s history. (I often want to go back and open other results, too.) Link to comment Share on other sites More sharing options...
Andrew Posted August 7, 2019 Share Posted August 7, 2019 I am well aware how useful a generalised "Keep Alfred Open for a bit" would be, and do have some internal notes on this already. Any change like this would be a holistic change within the framework, so would be quite involving. Either way, it's on my radar. vitor 1 Link to comment Share on other sites More sharing options...
leowoods Posted October 1, 2022 Share Posted October 1, 2022 Bumped into this today. I have a workflow that uses a List Filter to ask whether I want to include a link, and then a keyword node to inquire the link. If I don't want to have a link, I need the above workaround as without, when not selecting to include a link, the Alfred window remains open. I only learned about this today, which is more than 3 years that the workflow worked as intended. Just today, I had to update all my workflows and include a modifier to close the window. I'm very puzzled about this... Link to comment Share on other sites More sharing options...
vitor Posted October 2, 2022 Author Share Posted October 2, 2022 @leowoods If I understood you correctly, that is not the same thing and the proposed solution wouldn’t help. In your case, what makes sense is to add the Hide Alfred Utility. Link to comment Share on other sites More sharing options...
leowoods Posted October 3, 2022 Share Posted October 3, 2022 Hi @vitor, Thanks for the follow-up! If I don't need the modifier, and I can use the utility, how can I have the window remain open for path one, and closed for path two? The workflow can be downloaded here: https://cdn.zappy.app/296e6ea8fb5cfaef75b78d10dee312d0.zip If I understand how this test workflow should work, I should: 1. Be able to add a note, assign it to a variable, select "yes" and then add a link, output is Path One 2. Be able to add a note, assign it to a variable, select "no" and it should output Path Two and close the Alfred window I'm only able to close the Alfred window if I enter CMD + return (even though I didn't specify any modifier in this workflow). How come it only closes when using the CMD modifier? How would I set up the workflow that for path one, the window remains open and I can add a link (keyword input), and how it close when selecting "No" in the List Filter action? Thanks! Link to comment Share on other sites More sharing options...
vitor Posted October 3, 2022 Author Share Posted October 3, 2022 You add the Hide Utility on the bottom path: leowoods 1 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