luckman212 Posted February 11, 2022 Posted February 11, 2022 (edited) macOS 12.2.1 Alfred 4.6.3 [1284] Here's an example Workflow to illustrate the (bug?) https://github.com/luckman212/alfred_bugs/blob/main/uid test.alfredworkflow.zip?raw=true Type "uid x" to invoke it, then try actioning the 2nd or 3rd item (they are all set to valid: false). Now, if you type "uid x " (note extra space at the end!) the items maintain the correct sort order. Here's a video... https://user-images.githubusercontent.com/1992842/153678417-f6c2174b-f936-43d9-8193-e33f5ba3eb0b.mp4 Edited February 14, 2022 by luckman212
luckman212 Posted February 14, 2022 Author Posted February 14, 2022 I haven't tested with the previous "official" build FYI so not sure if this is a new bug introduced in the latest beta
Andrew Posted February 15, 2022 Posted February 15, 2022 @luckman212 interesting spot, thanks. I couldn't get a fix for this into the 4.6.3 release (earlier today), but I'll have it fixed for the first 4.6.4 pre-release in the nearish future. luckman212 1
Andrew Posted March 8, 2022 Posted March 8, 2022 This should now be fixed in the 4.6.4 b1289 pre-release luckman212 1
Andrew Posted April 28, 2022 Posted April 28, 2022 Sorry, this fix is going to have to be rolled back as it breaks a fundamental part of latching results within Alfred. Placeholders (e.g. filter inputs which yet to have an argument typed) are treated in the same way, so they no longer get filtered to the top on keyword latching. I will add a ticket for a more considered fix in the future. Cheers, Andrew
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