![]() Modifying the dropped file’s path is possible with the Run AppleScript action. There is, thus, no way to modify the dropped file’s path using either an AppleScript variable or a Shell Script variable in order to get the dropped file’s base name. ![]() As far as I can tell, the variables are all, basically, static, even if in a dynamic way. There is no variable that contains the dropped filename, however, and the AppleScript/Shell Script variables don’t take any arguments. ![]() There is no option to tell it to take one of the dropped files and use that as its new filename.Īutomator has some very impressive variable options: there are variables that are really AppleScripts, variables that are really shell scripts, variables containing many system names and common system paths. This runs a different workflow, and can send its own dropped items one at a time to that second workflow.īut, there’s a second problem: the Combine PDF Pages action creates files with a random filename. For that, we need the Run Workflow action. It doesn’t do anything to incrementally loop through the list of dropped files. How to prepend the disclaimer to hundreds of files? Automator has a loop workflow action, but all it does is go back to the beginning of the workflow. However, this only works for one file at a time. Automator can loop through dropped items one at a time using Run Workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |