esceef Posted March 13, 2014 Share Posted March 13, 2014 I created a workflow to open 3 files (Filemaker files). All files are password protected. Normally I start one file, put in a password and it opens. The Alfred workflow ends with the first file :-(. This is the same for a keyword and a shortcut workflow. How can I get, what I want ? Link to comment
jdfwarrior Posted March 14, 2014 Share Posted March 14, 2014 I created a workflow to open 3 files (Filemaker files). All files are password protected. Normally I start one file, put in a password and it opens. The Alfred workflow ends with the first file :-(. This is the same for a keyword and a shortcut workflow. How can I get, what I want ? Are you just just passing all 3 files at once for Filemaker to open? If so, perhaps you should make it loop through all files and open each one individually to see if it would prompt for the password for them that way Link to comment
esceef Posted March 14, 2014 Author Share Posted March 14, 2014 How can I "make it loop through all files and open each one individually“ ? Link to comment
rice.shawn Posted March 14, 2014 Share Posted March 14, 2014 Link a keyword to a script action as "bash" the script should be: open "/full/path/to/file/1.filemakersextension" open "/full/path/to/file/2.filemakersextension" open "/full/path/to/file/3.filemakersextension" If that moves too quickly, then you could try: open "/full/path/to/file/1.filemakersextension" wait open "/full/path/to/file/2.filemakersextension" open "/full/path/to/file/3.filemakersextension" If it is still too fast to open the third, then put in another "wait": open "/full/path/to/file/1.filemakersextension" wait open "/full/path/to/file/2.filemakersextension" wait open "/full/path/to/file/3.filemakersextension" Link to comment
esceef Posted March 14, 2014 Author Share Posted March 14, 2014 hmm, no tip works the way I want. Only the first file will be opened. But: as I used three times the same keyword (after I had put in 2 passwords for the first, and second file) the files will be opened one after the other . Using Log "All Information" for selected [Run Script] object in this workflow at the end the debug window shows: [iNFO: alfred.workflow.action.script] Processing output 'alfred.workflow.output.notification' with arg '' [iNFO: alfred.workflow.action.script] Processing output 'alfred.workflow.output.notification' with arg '' [iNFO: alfred.workflow.action.script] Processing output 'alfred.workflow.output.notification' with arg '' This left e big ? for me. Any parameters I had to activate or deactivate ? Any number to the "wait" parameter to let the script be active ? Link to comment
rice.shawn Posted March 14, 2014 Share Posted March 14, 2014 There are a few other hacky things to try. One would be to make a single keyword and have it point to three script actions that will open a file, one for each. That might make it work correctly. Otherwise, you might try your hand at an Applescript that would tell finder to open the three files. The latter one might have more luck. Unfortunately, I don't use filemaker and don't have encrypted documents to test this sort of thing on, so I'm probably not much more help. Link to comment
esceef Posted March 14, 2014 Author Share Posted March 14, 2014 I made a test with three password-protected pdf-files. This works better. All three files were opened and waited at the end of the workflow for password input. It seems that Filemaker stops opening the second file as the first waits for a password entry. Link to comment
esceef Posted February 11, 2016 Author Share Posted February 11, 2016 Hm, almost 2 years later and still no good solution with Alfred 2 ? Link to comment
deanishe Posted February 11, 2016 Share Posted February 11, 2016 That's because the problem isn't with Alfred, it's with Filemaker. Alfred simply tells OS X to open the file(s) using the standard API. OS X then tells the relevant application to open the file(s). Any issue you're having is with that application, not OS X and not Alfred. The best you can do with Alfred is to try and work around the problem with Filemaker. If that doesn't work, it's still Filemaker causing the problem. Link to comment
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