rjames86 Posted April 29, 2014 Share Posted April 29, 2014 Hey guys, I'm not sure if this is by design or a bug, but figured I would throw it in this topic for the time being. In 2.3 pre-release, I'm starting to use external triggers. I've noticed that when sending one trigger to another (a script filter in this case), the title and subtitle text do not appear. Note: I'm firing the external trigger with no argument: tell application "Alfred 2" to run trigger "admintype" in workflow "com.alfredapp.andrew.xmlformat" The resulting external trigger looks like this: Whereas if the trigger is called separately it appears as this: It would be great to show at least the subtitle text so that it's intuitive what is being asked in this prompt Thanks! - Ryan Link to comment Share on other sites More sharing options...
Tyler Eich Posted April 29, 2014 Share Posted April 29, 2014 I've replicated this, but I believe it's the intended behavior. Just to clarify: you want the keyword's Placeholder Title and Subtext to appear when the keyword is triggered? Alfred 2 v2.3 (263) on Mac OS X 10.9.2 (13C64) Link to comment Share on other sites More sharing options...
rjames86 Posted April 29, 2014 Author Share Posted April 29, 2014 I've replicated this, but I believe it's the intended behavior. Just to clarify: you want the keyword's Placeholder Title and Subtext to appear when the keyword is triggered? Yep exactly. Just something to display what the prompt is asking for. Otherwise, the only way to know would be the icon, which isn't ideal Link to comment Share on other sites More sharing options...
Tyler Eich Posted April 29, 2014 Share Posted April 29, 2014 Yep exactly. Just something to display what the prompt is asking for. Otherwise, the only way to know would be the icon, which isn't ideal I agree. I don't like the current behavior either. Link to comment Share on other sites More sharing options...
Andrew Posted April 29, 2014 Share Posted April 29, 2014 This is the same behaviour as linking a hotkey to an input, and I agree, it's not ideal. I'll have a think about what I'll do to rectify this Link to comment Share on other sites More sharing options...
jdfwarrior Posted April 30, 2014 Share Posted April 30, 2014 Hey guys, I'm not sure if this is by design or a bug, but figured I would throw it in this topic for the time being. In 2.3 pre-release, I'm starting to use external triggers. I've noticed that when sending one trigger to another (a script filter in this case), the title and subtitle text do not appear. Note: I'm firing the external trigger with no argument: tell application "Alfred 2" to run trigger "admintype" in workflow "com.alfredapp.andrew.xmlformat" The resulting external trigger looks like this: Whereas if the trigger is called separately it appears as this: It would be great to show at least the subtitle text so that it's intuitive what is being asked in this prompt Thanks! - Ryan I mentioned this to Andrew as well. As a temporary workaround... make the external trigger point to a keyword (but don't set the keyword), set the title and sub on it and set the argument to optional Link to comment Share on other sites More sharing options...
rjames86 Posted May 3, 2014 Author Share Posted May 3, 2014 I mentioned this to Andrew as well. As a temporary workaround... make the external trigger point to a keyword (but don't set the keyword), set the title and sub on it and set the argument to optional Thanks David. Not sure this would work with the workflow I'm going for. My idea right now is something like this: Keyword "argument" > Script filter with searchable options > Run Script > Open URLs If in step two, I were to use a keyword filter instead of script filter, I wouldn't be able to search for additional options. This is the same behaviour as linking a hotkey to an input, and I agree, it's not ideal. I'll have a think about what I'll do to rectify this Thanks, Andrew. Really loving this new external trigger stuff. I'm just getting into Keyboard Maestro, and see a ton of potential here too Link to comment Share on other sites More sharing options...
Andrew Posted August 18, 2014 Share Posted August 18, 2014 Hey chaps, Just a quick update to say that I'll be reorganising the Alfred window in 2.5 for the case of a fixed input such as a hotkey or external trigger which shows Alfred. This also helps with things like web searches setup for the upcoming Alfred Remote. The relevant input icon which was previously to the left will move to the right (replacing the Alfred hat, if visible), and the input itself will be processed. This essentially means that a keyword / script filter will be run regardless of whether an argument has been specified... basically, you'll get the placeholder text or your initial results without having to fudge things. Here is an example: Tyler Eich 1 Link to comment Share on other sites More sharing options...
rjames86 Posted August 18, 2014 Author Share Posted August 18, 2014 Thanks, Andrew! Link to comment Share on other sites More sharing options...
Andrew Posted September 8, 2014 Share Posted September 8, 2014 If you update to 2.5 b290 pre-release, you will now see this new behaviour - let me know how you get on Link to comment Share on other sites More sharing options...
rjames86 Posted September 9, 2014 Author Share Posted September 9, 2014 Thanks again for looking into this. This is very useful. I'm going to keep playing with this and let you know if I have any more feedback. The only thing I can think of is still to have subtitle text, but I'll see if I really end up needing it Link to comment Share on other sites More sharing options...
Andrew Posted September 9, 2014 Share Posted September 9, 2014 Thanks again for looking into this. This is very useful. I'm going to keep playing with this and let you know if I have any more feedback. The only thing I can think of is still to have subtitle text, but I'll see if I really end up needing it What do you mean, the subtitle text? Link to comment Share on other sites More sharing options...
rjames86 Posted September 9, 2014 Author Share Posted September 9, 2014 (edited) Sorry, not subtitlle, Placeholder Subject from the script filter: I'm writing a lot of workflows that are used by other people and so having *some* instructions for them is always helpful. The results of the script filter should be enough of a clue, but not always Edited September 9, 2014 by Ryan M Link to comment Share on other sites More sharing options...
Andrew Posted September 10, 2014 Share Posted September 10, 2014 Sorry, not subtitlle, Placeholder Subject from the script filter: I'm writing a lot of workflows that are used by other people and so having *some* instructions for them is always helpful. The results of the script filter should be enough of a clue, but not always Ah yeah, there are some odd behavioural things around this still too... I'll look at this now and see what I can do, cheers Link to comment Share on other sites More sharing options...
Andrew Posted September 10, 2014 Share Posted September 10, 2014 Sorry, not subtitlle, Placeholder Subject from the script filter: I'm writing a lot of workflows that are used by other people and so having *some* instructions for them is always helpful. The results of the script filter should be enough of a clue, but not always Could you update to the 2.5 b293 pre-release and try again, the behaviour in this area should now be fixed! Link to comment Share on other sites More sharing options...
Andrew Posted September 10, 2014 Share Posted September 10, 2014 I'm also going to make a small change which uses the workflow icon to the right if it's set, otherwise it uses the script input icon like this... Link to comment Share on other sites More sharing options...
Andrew Posted September 10, 2014 Share Posted September 10, 2014 If you update to 2.5 b295, you should see this image behaviour change now Link to comment Share on other sites More sharing options...
rjames86 Posted September 10, 2014 Author Share Posted September 10, 2014 Great call on the icon. I'm terrible about adding special icons for each part of the workflow. I think we might be talking about two things. The subtitle text for each of the items in the script filter have always appeared fine. What doesn't appear (also in your last screenshot) is the placeholder subtext for the script filter itself. I have a workflow that takes a file action → script filter via an external trigger That script filter looks like this When I run the trigger, I see all of the entries along with their title and subtitle text, but the placeholder subtext doesn't. After a little more testing, it looks like if I add a keyword to the script filter and begin to type the keyword, the placeholder subtext appears up until the point where you enter a keyword Maybe I was requesting something that never really existed in the first place. I was just hoping to have some sort of placeholder text just above the listed entries to tell the user what they're looking at or what to do with it. Link to comment Share on other sites More sharing options...
Andrew Posted September 10, 2014 Share Posted September 10, 2014 Great call on the icon. I'm terrible about adding special icons for each part of the workflow. When I run the trigger, I see all of the entries along with their title and subtitle text, but the placeholder subtext doesn't. It looks like it's working as expected in this case... the placeholder is there to show what's happening in Alfred's default results. When directly triggering a script filter, the results have subtly different behaviour depending on the argument type. With a 'required' argument, the placeholder is shown until an argument is typed. With Optional or None, your script is run immediately (same as default results) which naturally allows you to select a generated result when the argument is empty. Link to comment Share on other sites More sharing options...
rjames86 Posted September 10, 2014 Author Share Posted September 10, 2014 It looks like it's working as expected in this case... the placeholder is there to show what's happening in Alfred's default results. When directly triggering a script filter, the results have subtly different behaviour depending on the argument type. With a 'required' argument, the placeholder is shown until an argument is typed. With Optional or None, your script is run immediately (same as default results) which naturally allows you to select a generated result when the argument is empty. ahhhh okay. perfect. Thanks for clarifying. Thanks again for all your help on this. External triggers have been amazing. Once I finish polishing up my Dropbox workflow, I'll be sure to post it on the forum. It makes a lot of good use of external triggers + script filters Link to comment Share on other sites More sharing options...
Andrew Posted September 10, 2014 Share Posted September 10, 2014 ahhhh okay. perfect. Thanks for clarifying. Thanks again for all your help on this. External triggers have been amazing. Once I finish polishing up my Dropbox workflow, I'll be sure to post it on the forum. It makes a lot of good use of external triggers + script filters Excellent, thanks for your help and feedback on this 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