Jump to content

imurban

Member
  • Posts

    38
  • Joined

  • Last visited

Posts posted by imurban

  1. Hi dsburfitt.

     

    I'm very late to the conversation here, but I hoped to find if you were ultimately able to get the Applescript to work just by replacing that first line with dfay's recommended "POSIX" line. With that edit, I can file-action my script to run as far as activating InDesign (CS6 in my case…changed the app's name in my script), but no placement of the Alfred-actioned file occurs. From what I read of Applescript in InDesign, it shouldn't matter that I'm attempting this with CS6 rather than CC 2017. Just wondering if you needed to otherwise tweak you original script to get it working. Thanks for your time.

  2. On 10/12/2017 at 4:22 PM, xilopaint said:

    Oh, I didn't know the workflow worked with Things 2. In this case I might consider to set the icons of Anytime and Upcoming lists for Next and Scheduled. What do you think about this idea?

     

    Besides that, is there any workflow feature not working with Things 2?

     

    Sorry to respond so late. Using those icons from the Anytime and Upcoming lists would look great. I'm still heavily using both versions of Things, so this workflow has been a real help. The new Areas icons look sharp, too. Thanks for all your work on this.

  3. Probably just my bad use of tech terminology! I just meant to say that when I am only running Things 2 (for organizing my job workload), your workflow works with it, indicating the old foci ("Next", "Scheduled") with the Areas icon. When run both versions of Things simultaneously, the workflow conveniently interacts only with Things 3 (no conflicts). I'm attaching an image here to demonstrate. Anyway, it's a helpful bonus.

     

    Screen Shot 2017-10-12 at 3.08.02 PM.png

  4. I found a really cool way to get 2do to play ball with alfred: Register a custom URL! The following one just searches 2do for tasks. Drop the following line in your browsers' url bar to do that.

     

    alfred://customsearch/Search%202Do%20for%20%7Bquery%7D/2do/utf8/noplus/twodo%3A%2F%2Fx-callback-url%2Fsearch%3Ftext%3D%7Bquery%7D

     

    I would love to get this to work, but I must be misunderstanding your instruction. Pasting that string into my browser returns a top search engine result to this thread.

     

    On the other hand, pasting the string into Alfred's quick entry pane imports a custom search under "Web Search" in Alfred's preference panel with a keyword of "2do", but when I invoke Alfred, type that keyword and enter a search term, Alfred prompts for a target application, and 2Do.app is greyed out. 

     

    What am I missing?

     

    jYxUOsZ.png

     

    8fRHLnu.png

     

    4HzLxlW.png

     

    UdWFmSb.png

     

    ZhwsllF.png

     

    lYemFs1.png

     

    vjG9jND.png

  5. Thank you, deanishe. I'm glad to know I'm not missing something about the core functionality.

     

    Would you (or anyone) happen to have an Applescript to share that does what you described? Not knowing how to write applescript myself, I'm still confident I can repurpose such a script to target my applications. I already use a lot of applescripts with Alfred, mostly cobbled from bits an pieces people have shared on these forums.

  6. @dfay

     

    Thanks for your response. Looking over your two recommended approaches, I don't think I want to change any setup of my applescripts in pursuit of this hotkey behavior.

     

    To clarify, I'm after the sort of functionality described in the "Top tip" called out in yellow on this documentation page: http://support.alfredapp.com/workflows:config:triggers-hotkey

     

    I've figured out a lot in Alfred, but the hotkey behavior that doc page describes has me really confused. Can anyone attest to having setup two identical hotkeys with "Action: Show Alfred / Argument: Text / Text: {specific to related app(s)}"?

     

    If not, can anyone demonstrate how identical hotkeys with different contextual output work out of the box in Alfred?

  7. Does this functionality require that the hotkeys directly trigger applescripts (which scripts also requires some tinkering to cooperate). Am I right to figure this is no solution if I want identical hotkeys to load Alfred's window with variously predefined text?

     

    In my case, depending on which app I have focused, I was hoping a single hotkey could load Alfred with certain characters (differentiated by separate instances of the hotkey). This text input would result in an Alfred dropdown menu of keyword-linked applescripts (already defined in workflows setup for each given application).

     

    I already use different text-triggering hotkeys to call on identically key-worded applescripts in various workflows. I was hoping I could just use one hotkey to enter different workflows depending on the app in focus and thereby cut down on friction.

     

    So, with that aim in mind I deleted all the hotkeys from their respective workflows and redefined them in a separate workflow (named "Hotkeys") as the official documentation seemed to indicate I must.  Separating text-triggering hotkeys from the workflows containing their associated keyword-launched applescripts does not interfere with functionality.

     

    Within the "Hotkeys" workflow I began recreating the hotkeys one by one, first defining their distinct text output and then targeting different "related apps" for each hotkey. Still, I am prevented from defining any two with the same key combo.

     

    Why won't this work?

  8. Hello Alfred Community!

     

    I need your help. I mistakenly entered a crucial string of numbers related to me by telephone into Alfred without actioning it. Sad to say, it was a license plate number from a criminal incident (attempted abduction). Talk about a dumb move on my part! Panic does things like that. But that's how much I've come to rely on Alfred – invoking it in an emergency instead of grabbing pencil and paper!

     

    If the developers could somehow help me retrieve a day's worth of typed queries (perhaps from some file I can output from Alfred?), a Massachusetts police dept. could be helped greatly in this matter. Not knowing about the "typed query history" access (or its limits) until much to late, I employed Alfred in numerous google searches about keystroke capture which pushed the license plate number out of Alfred's 20 query memory. :(

     

    For my part, I'll do whatever it takes, even providing all the sorry details of the scoundrels' attempt in hopes of whetting your appetite for justice.

     

    Please let me know if this is possible or not!

     

    Thanks for your time.

     

    Ben

  9. I'll look into it, but the workflow currently just pulls all the tasks from the database without attending to where they're sorted.

     

    That would be flat out incredible. It's very easy to get drawn into tweaking every corner of my database, when what I meant to do was just glance at the Today list!

     

     

    I was wondering if there's something wrong with my workflow because every time I add a new To-Do, it changes focus to the app. Ideally, I would like it to return focus to the application which I came from.

     

    Another great request. This would really speed things up for me, too. Alfred's notifications already do the trick of assuring me the task was received.

     

    This is one of the most valuable workflows for me in Alfred. It has help me considerably over the past year. I really hope it is kept fresh!

  10. Thank you all for your advice. In the final estimation, I haven't really got competency to string it all together. I should be able to get by just keywording applescripts from Alfred that run specific Photoshop actions individually on open images. If I really need to batch process, I can just initiate those PS actions on whole sets of images from Bridge.

     

    Again, I appreciate all the thoughtful responses. I'm happy to push Alfred to the limits of my capabilities, confident that smarter folks than I are really making it do some dazzling things. I will say, I am now very mindful of SIPS as a future option should my cobbled approach get too cumbersome. Thank you also for that.

  11. You probably want to get rid of that "Get Specified Finder Items" action.

     

    Instead of a Workflow, try creating an Application with Automator. Then, instead of calling automator from your bash script, use:

    open -a /path/to/your/jpeg_sRGB_1000.app "$i"

     

    Thanks, deanishe.

     

    Unfortunately, I can't get that modified Automator approach to work, even on a single Tiff file passed by File Action. It does manage to copy (via Copy Finder Items in Automator) my entire user.workflow folder to the destination folder!

     

    I am now trying to work out that sips suggestion of yours that Shawn Rice picked up on.

  12. Yes. Thank you. Your explanations and examples help a great deal. Very kind of you to take the time with me.

     

    Unfortunately I can only get the workflow to output one (the last) of my Alfred buffered files (I tested three Tiff files). Perhaps it's the number of steps in my Automator workflow that causes a time-out of sorts?

     

    Below are screen shots of my File Action, Run Script Item, and Automator workflow. Could you please tell me if these shed any light on it?

     

    QJFzL1K.png

     

    4hsrRCA.png

     

    fMQxOHK.png

  13.  

     

    You can call automator from a Run Script item using the automator command from the command line.

     

    I appreciate the response. I don't even know what the above quote means (Ha! I'm so in over my head!) I hoped it was just a matter of tweaking my approach, but If it's not immediately obvious to someone with your expertise, then it's probably way too far in the tall grass for me :)

     

    Could you tell me if this same limitation of file actioning a batch of images applies with Applescript (vs. Automator)? If it's just a obstacle with Automator, I'm happy to investigate Applescript solutions. I just want to keep it all in Alfred! 

     

    I've looked up and down the forums, but I can't seem to find any example of file action to Automator and/or Applescript to resize image files. If I could find something functioning along those lines, I'm sure I could adapt it to my needs.

  14. Hello all.

     

    Looking for some simple directions, as I'm not skilled at scripting in the least.

     

    I've had success creating keyword-initiated workflows that run Automator workflows on selected Finder items, but I am completely stumped as to how I should structure and then run an Automator workflow (or app) as the result of an Alfred "File Action".

     

    My successful Automator workflows (triggered by Alfred keywords) function because the targeted Automator workflows all begin with "Get Selected Finder Items".

     

    But for this new Alfred workflow (pointing to an image resizing workflow in Automator) I'm trying to bypass Finder and pass multiple images (file buffered through Alfred) to the Automator workflow by means of an Alfred "File Action"

     

    In this case, I supposed (maybe mistakenly) that my Automator workflow shouldn't begin with that "Selected Finder Item" call. So, I dropped that out…still the "File Action" doesn't run the Automator workflow on the specified image(s).

     

    Could you please help me figure what I must change with my Automator workflow, Alfred Workflow setup or both?

×
×
  • Create New...