Setting the Template Structure
Once a GridTemplate is scanned, Q++ requires information on how to interpret this GridTemplate. It is the combination of the scanned GridTemplate and the way you instruct Q++ to treat it that make up a Template. The guidelines for GridTemplate creation are covered in Designing GridTemplates in QuarkXPress.
The structure of a Template is set in the Template Properties dialog.
In that dialog, the options Structure and Additional Structure depend on the type of structure. Each type of grid structure is discussed separately below, but first it is important to understand the respective roles played by the structure set here and the tokens' DayValues, in determining the date of a given token in a grid :
•The structure you associate with a Template tells Q++ that, in the case of a weekly grid, the starting date of each copy of the grid is always one week later.
•However, it is the tokens' DayValues which then give the date of each token. On a given copy of a grid the date of a token is the minimum date of the grid plus the DayValue.
It is important to understand the above mechanism, because setting a grid's structure to weekly, will not stop Q++ from displaying a month, if that grid has 30 different DayValues. What it will do, however, is display a slice of 30 days that start 7 days later with every copy of the grid. This method is actually used for yearly grids.
When you select Days, Weeks, Month or Years, Q++ tries to guess from the list of tokens, how many day, weeks, months or years are contained in the current GridTemplate. You can then modify that value.
Finally, it is important to note that scanning a GridTemplate does not insert magic codes into the GridTemplate. You are simply saving a way of looking at this GridTemplate (that is why you can use the same GridTemplate as 2 different Templates, one being a daily the other being a weekly).