The 'tag' logo image variables (those with 'tag' in their names) are replaced in setup sheets by a complete HTML image tag of the form:
<img width="100%" src="image-filename">,
which expand in the HTML document to fill the available space (for example, a table cell) while maintaining the aspect ratio.
Whenever this is unsatisfactory, the 'source file' image variables (those without 'tag' their names) should be used instead, to construct the <img> specification explicitly with the following (X)HTML tag: <img width=n height=n scr={variable}>, where width and height are optional parameters you can use to control the size of the image. For example:
<img width=50 height=40 src="$project.CompanyLogo$">
These variables are best used in the header and summary template types at an NC-level (for example, Header.html and Summary.html). You can also insert them into the toolpath template types. If you've got more than one NC program, and you want to add these variables to the summary template types at a project level, place them between the <summaryrow> </summaryrow> tags in the toolpath context. For example,
<summaryrow> <tr> <td>${toolpath.Name} <br /> ${stoolpath.TapFile}</td> <td>${ncprogram.SpecialName}</td> <td>${toolpath.Strategy}</td> <th>Type</th><${tool.Type}</td> </tr> </summaryrow>
Here the variable ${ncprogram.SpecialNames} refers to the NC program that contains the corresponding toolpath, and therefore, will be resolved. If you place ${ncprogram. SpecialNames} separately, it is not evaluated correctly.
These variables should be used in the toolpath template types (for example, Toolpath.html). If you want to use them in the summary template types, place them between the <summaryrow> </summaryrow> tags in the toolpath context. For example:
<summaryrow> <tr> <td>${toolpath.Name} <br /> ${stoolpath.TapFile}</td> <td>${tool.Identifier}</td> <td>${tool.Number.Value}</td> <td>${tool.TipRadius}</td> </tr> </summaryrow>
Here the variable ${tool.Identifier} refers to the tool that is used by the corresponding toolpath, and therefore, will be resolved. If you place ${tool.identifier} separately, it is not evaluated correctly.