Jump to content

Search the Community

Showing results for tags 'parameters'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 4 results

  1. Hi there is there anyway to launch an application (e.g. Marked 2) with a specific path? I'm trying to open a file with an application that I wish for Alfred to launch, so something along the lines of: "marked 2 <path to file>" Should hopefully open the file in marked 2. Thanks!
  2. Hey guys, Say I make a Script Filter and link it to 4 script actions that each perform a different function, but each action needs a different input from the Script Filter, and this is where the problem begins, because the "arg" attribute can hold only one value which will work with just 1 of the 4 actions Right now the only workaround to this problem is to give the "arg" attribute a separated list of multiple values, and then each action would need to parse the input and search for its piece of data, but it's too much parsing and splitting involved.. My opinion is that we should have some freedom in the XML attributes of the feedback results by letting us define our own attributes in a result and Alfred would automatically send those attributes as individual parameters to the "alfred_script" function, as well as individual {attribute_name} to other predefined actions. For example, script filter would generate this xml result: ... <item uid="rdioartist" arg="r96664" valid="yes" autocomplete="Incubus" artistiname="Bjork" track="All is full of love"> ... And we, the programmers, would then use the following in script action: on alfred_script(arg, artistname, track) -- we use the parameter that is needed for a specific action end alfred_script [later edit]: a big problem with the current design is when you link a script filter to multiple actions AND a Notification action, because inside the Notification action we can't split the separated list of values of the "arg" attribute, and setting the arg attribute to a single value would make the other actions useless So with my suggestion above we would type something like {aristname} or {track} inside the Notification action
  3. Is it possible to provided multiple parameters to a workflow? I tries {query0} {query1} / {query1} {query2} neither of the above worked. And if we give {query} {query} they both are the same values, so should I be passing it to a shell script and then work out the logic there and then invoke my operations accordingly?
  4. Hi All, I've just started tinkering with Workflows after finally buying the Powerpack. The first idea that came to my head was to setup a quick trigger to run the show/hide hidden files command in Terminal. Very useful when you're looking .htaccess files etc - and it saves me googling the command every time I want to run it. At the moment I've got two separate workflows - one for hiding, one for showing. Set up on different keywords hiddenhide and hiddenshow. That works fine, but it doesn't seem very elegant. I ideally wanted to combine them into a single Workflow I could run using a parameter. I just couldn't work out how to do it. Ideally I'm thinking using 'hidden show' 'hidden hide' wrapped in one workflow would be much neater. I'm sure I've missed something obvious. Any ideas?
×
×
  • Create New...