Since version 0.3 you are able to selectively apply settings from a template of your choice to any job you like. One reason might be that you want jobs that have already been recorded to be recorded using different config settings (e.g. other quality settings, resolution, etc.). If you wanted to do this for many jobs at once, it would be very tedious to edit each job manually, setting up changes.
You can apply properties of templates very easily:
Select the template you want to use
Select the job(s) whose properties you want to be affected by the template
Right-click inside the jobs table and select “Apply template”
A new dialog will open where you will be able to select which one of the settings should be copied from the template to the job. Please, be aware that old settings of the job will be overwritten!
Usually the settings will be copied 1:1 from the template to the job. There are 2 exceptions, though:
Demo directory: Here copying the value from the template to the job would not make sense, because in a template you actually specified a directory, not a file. However, a job needs to point at a file. What will happen shall be demonstrated by the following example: Let's say that the job's path to the demo file (before applying the template) has been C:\Nexuiz\data\demos\mydemo.dem and the path setup in the template has been pointing to the directory C:\Games\Nexuiz2.5.2\data\demos. The new demo file path, after the “apply” process is done, would be C:\Games\Nexuiz2.5.2\data\demos\mydemo.dem; this means that from the job's demo path the program will just take the name of the demo by itself (mydemo.dem), and put the path from the template in front of it
Video destination: Here the same thing happens like for the Demo directory. The new video destination will be <Directory set up in the template> + <just the filename of the setting of the job>
Another example of how this feature could be useful is this one: Suppose some movie maker was to create a community movie with frags from different people, or a movie maker was to continue or finish a movie from someone else. If one person creates a queue of jobs (which naturally includes the demo's names, start second and end second) and then decides not to record the frags herself but send it to some other movie maker, all that needs to be done is to save the job queue and send it to the other movie maker, together with the demos. The other movie maker can then copy the demos into his own demo directory and import the job queue. Of course the problem would then be that all these imported jobs could not really be executed right away, because all these paths might be incorrect, I mean, would simply not exist or match to the system of the movie maker who wants to record the jobs (e.g. path to Nexuiz engine or demo directory). But this can easily be fixed. The movie maker just needs to select the imported jobs and apply one of her own templates to them, and by doing so, fix all incorrect paths.