In short, "no".
The issue is the destination folder which is driven by the batch dialog. Once you run the batch dialog, be it droplet or automate|batch, the dialog will take control of the source AND destination of the files upon which the actions are performed.
In addition, I’m not sure what will happen when you run a batch, that includes multple Save As statements – IF that works, it shouldn’t be too hard of a job to sort by extension post processing and manually move them.
But that’s an "iffy" process that I would want to test first.
If it were me, because I’m a conservative anal-retentive type when it comes to this sort of thing, I would create 4 separate batch actions, be they droplet or run from the File|Automate|batch. It’s cleaner and more predicable, and you can always get coffee while they process <grin>.
Btw, I have yet to see an inherent advantage of droplets, except for portablility. That is, you can bring it to work or give it to a friend. Other than that, functionally, running File|Automate|Batch is the same thing, without creating an EXE. <shrug>
Peace,
TOny
Ahhh… Thanks so much for yor input. I messed around a little, creating 4 separate droplets, and sure enough things are pointing toward the batch commands. So, while I can’t automate my entire day *snicker*, at least I can streamline a little. If I stumble on something life-changing however, I’ll post the results. A droplet’s portability is really nice since I work with designers in other buildings in a big network. Our files reside on a server, so if the droplets were on there, everyone could use them. Oh well, we’re no quite there I guess! Thanks again for the advice,
Paul-
