Appearance, Styles and Templates

Previous pageReturn to chapter overviewReturn to Top Next page

 

 

 

 

 

 

 

 

SVDesigner

 

 

SVDESIGNER provides several useful features to aid in the visualization and presentation of user data. These features fall into four general categories: View, Appearance, Styles and Templates.

 

View

 

Settings that are part of the view affect the display of all data in the current project. They include the ability to alter the world coordinate system, scale the data, and toggle various user interface elements such as the axes or bounding box. These settings are stored with the SVDESIGNER project file.

 

Appearance

 

Most geometry objects have settings that control how they appear on the display. These settings are unique to the object and can be modified at any time. These settings are saved with the model.

 

Styles

 

Styles are a named collection of display settings for a specific type of object. For example, there are point styles, line styles and fill styles. Geometry objects are assigned a specific named style by the user, and any object assigned that style will use the same properties. Styles can be modified by the user, and these changes will affect all objects using that style.

 

Note that not all geometry object types support all styles; in particular, scatter data does not require a line or fill style, polylines do not require a fill style, and slices inherit their style from the objects being sliced.

 

Style information is stored in a template, which is automatically saved with the SVDESIGNER project file.

 

Templates

 

A template is the collection of all available styles stored into a template file. This file is automatically saved with every SVDESIGNER project file, and uses the SVT file extension. It is possible to load, save, and reset the template collection for any project, and re-use a template in multiple projects. There is no centralized "universal template" but it is quite possible to create a template file with a standard variety of styles for re-use and load that template into any project.

 

If the user wishes to manage their own templates, it is their responsibility to store these template files appropriately. The template file matching the file name of their conceptual model is automatically updated after the model is saved.