Editing Template Properties
Editing template properties
The Edit Template Properties window can be accessed by selecting
.
Properties
The Properties section contains the Title and Description for the current template which can be freely changed. The Read-Only property is immutable and signals whether the template can be overwritten. For library templates it is always checked; for user-made templates it is unchecked.
Tags
The tags list provides information about the current template that is used for filtering in the Choose a Page / Template windows. Tags can be added to the list by selecting a category and value from the drop-down menus and pressing . User-defined category-value pairs may also be added by typing directly into the Category and Value boxes instead of using the drop-down buttons. Tags can be deleted from the list by selecting them from the Tags list panel and pressing . The Type category determines the tab in which the template appears in the window.
Thumbnail
The thumbnail determines the image that is shown to represent the template in the Choose a Template window. This can either be generated from the first page of the template, or embedded from a separate file.
Generation
When generating image files for D3PLOT and T/HIS the preference controls what do do if an image with the same name exists. By default (selected) REPORTER will overwrite the image. However, you many want to run the same template multiple times for different models in the same directory. With this unselected a new image will be created for each model.
The preference controls how macros are replayed when generating a PRIMER object. When creating or updating a PRIMER object, REPORTER ensures that the MENU_AUTO_CONFIRM environment variable is unset so that any listing boxes created are not automatically dismissed. However in version 16.0 and earlier when generating a PRIMER object REPORTER would set the MENU_AUTO_CONFIRM environment variable. In some instances this could mean that the macro recorded in the object would not play properly (as when it was recorded the MENU_AUTO_CONFIRM environment variable was not set). From version 16.1 onwards by default REPORTER will now not set the MENU_AUTO_CONFIRM environment variable when generating PRIMER objects to be consistent. There may be very rare cases where this needs to be set when generating, in which case the preference can be used.
These preferences are not programme wide preferences. They are actually stored with the template and read/written as properties so they must be set for each active template.