niels_bom

Ah just discoverd another weird thing: When I have a List Filter Input and it's triggered by another object that passes an argument (an Arg and Vars Utility for example) strange things tend to happen. The argument from the previous object is passed in even though the LFI disallows it.

Problem description It took me little while to figure out why List Filter Inputs (LFIs) can be configured to have arguments. To be clear: I'm not talking about the `arg` of the items in the list. I am talking about the "Argument Required"/"Argument Optional"/"No Argument" setting of a List Filter Input. As I understand it: - When a List Filter Input has no argument: all items in the list are displayed and the user can not filter the displayed items. They can only select an item. - When a List Filter Input has an optional argument: all items in the list are displayed initially, the user can type text after the keyword of the LFI so it will only show items matching the typed in text. - When a List Filter Input has a required argument: no items from the list are displayed, matching items will appear when they type text after the keyword of the LFI. However: when a Hotkey Trigger is used to trigger an LFI that has the option set to "No Argument" it somehow is possible to type-to-filter items in the list. In Hotkey Triggers and Keyword Inputs an argument is something that's passed to the next workflow object. Which is entirely not the case for the argument in LFIs. In a Script Filter Input this setting is similar, but there the argument is used as an argument to the Script. To summarize: 1. I think calling this option "argument" for LFIs is confusing because the value is not used as an argument, it's only used for filtering the items in the list. 2. The option to have a required argument is strange: why would somebody want to build a workflow which is not forthcoming with the available options? (if there's a lot of them it should be a Script Filter Input). I don't see a valid usecase for this. Suggested improvements As a quick fix I think the documentation should state something like: I think the UI can be simplified by removing this option altogether and having the LFI always do filter-by-typing. I don't see any valid use cases for the other settings. If you're an Alfred developer and want to talk about this, feel free to contact me for a call.

I've got a Logitech MX Master 3, it has a horizontal scrollwheel but I think it's awkward to use. Can Alfred do the Space + drag?

(Alfred 5) Some of my workflows have a lot of items in them. More than the canvas (?) can show in one window. I can use my trackpad to scroll horizontally and vertically to reach those items. But I prefer using my mouse. Some macOS programs and webapps allow you to press the Space bar and drag the canvas around. One example is tldraw.com: Space + click and drag = move the canvas. Is this something Alfred can do or can be configured to do?

I see the exact same behaviour as OP. Can Alfred be configured to do this in a smarter way? Like 1. open the browser, 2 tell the single browser window to navigate to the given URL.

Silently failing sucks so hard. I want 45 minutes of my life back Apple...

How is this feature coming along? It would really make my life easier :-)