[delenca]

I have been meaning to ask this question for a while.

In Downloader Pro I would like to have a different set of settings associated with different jobs. i.e. If I am taking pictures from my dSLR I use a different download path, different image renaming settings, different IPTC compared to when I use my mom's P&S. I would like to have the ability to save and load a 300D.settings file or a A510.settings file i.e. which would automatically populate all my choices (Download path, etc). Is this available in any of the versions of DLPro? If not, I would recommend it as a good feature to add. Frankly, I always assumed that's what "Job code" was for, but clearly that's not it. Another name I suppose would be "templates".

I am working in Downloader Pro v. 1.7

Thanks,
-Alex

[DavidB]

This is a good idea, which I support. Something you don't suggest, but which would be a very useful addition, would be the opportunity to associate a saved IPTC data set with a particular settings file.

The Job Code is no more (and no less) than a piece of text you can use for any purpose with the %J/{J} token.

The facility you want does not exist in DL Pro at present, but there is something you can do. All the settings you mention are stored in the Registry key

HKEY_CURRENT_USER\Software\BreezeSystems\Downloade r\200

(or ...\201 for verions 2.0.x). You can save this key in regedit.exe to a suitable .reg file, where is any name you choose. If the settings file(s) is/are somewhere reasonably accessible (such as a folder with a shortcut on the desktop), you can easily double click on your chosen .reg file to load a particular set of settings before you start DL Pro.

Note that this process does not involve any of the more risky registry editing activities, only saving and loading settings data that the program itself has created.

DL Pro 2.0.x takes things a further step in the right direction by having a 'File|Export Downloader Pro settings' command, so that you can save the current settings from within the program and can leave regedit.exe well alone.

Hope this helps.