rice.shawn Posted March 19, 2013 Share Posted March 19, 2013 When I read this post (http://www.alfredforum.com/topic/1022-most-workflows-dont-work-resolved/), I remembered a bit of a potential problem that would keep some workflows from working: dependencies. I know that I don't have any authority here, but I'd like to suggest that when you post a workflow, with it you post dependencies — — OSX Version, min — Program Dependencies (if you have a link to a website, then that's great) & version #. — Your OSX version One example: I made a toggle command for "Caffeinate" (http://www.alfredforum.com/topic/710-toggle-caffeine/#entry3871), Caffeinate is native to 10.8., but it doesn't exist before that so. — Min OSX: 10.8 — Program "Caffeinate" (native in Mountain Lion — https://developer.apple.com/library/mac/#documentation/Darwin/Reference/Manpages/man8/caffeinate.8.html) — Tested: 10.8.2 ------- If might just be good to put down what version of OSX you're using to create it if there isn't any particular feature that you can identify. In the first thread that I referenced, the error was a renamed setting file from one OSX version to another, so this problem might be more common than we'd think. The same problem could creep up between program versions as well. ------ Please add in any other suggestions that might make sense for submitting information with the workflows. 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