|
||
|
|
||
Editing of table layouts is a functionality which needs deeper knowledge of SCIA Engineer and structure of its data and it is intended for more advanced users. Especially editing of result tables can be very tricky. It is recommendable not to edit layout of result tables.
Table layout editor is a tool for editing of table layouts (also called templates). Table layout editor is a special mode of Engineering Report. It uses the same UI components which are used in Engineering Report.
In the table layout editor the user can modify layout of tables or prepare a new layouts of edited table.
On the ribbon there are available all necessary actions:
The root item displayed in the navigator cannot be deleted and contains properties relevant for whole table.
Type of table defines the orientation of table header.
There are available following types of tables:
Simple form type of tables is intended mainly for result tables with set of sub-tables.
In case of Vertical tables it is possible to select from two variants:
The property Width of cells defines the way of calculation of table column widths.
This property controls displaying of sub-table with explanation of symbols used in the table. The sub-table is placed after the main table. See example with explanation of symbols used in the table of cross sections.
In case there is not available any explanation info for particular table, the sub-table is not displayed.
The property Splitting of table enables to split narrow tables into more columns.
Columns of tables which does not contain any valid value will be completely removed from the table if this property is checked.
This property is available for vertical tables only. If it is checked the first cell of a table is used as a header of one record. See the difference on following pictures.
This property is used for switching between two types of vertical tables:
It is possible to sort rows (in case of horizontal table) in table according to any displayed value.
Sorting can be controlled in Table layout editor using sorting icons on the Navigator. Following picture displays case when table is sorted ascending according to value Coord X.
It is also possible to sort table according to multiple keys.
In this case Coord X is used as a primary key and Coord Z as a secondary key. The priority of sorting keys goes according to order in navigator from the top to the bottom.
Table items can be grouped together into table cells. One cell represents one column in case of horizontal tables. In case of vertical tables the meaning depends on the variant of vertical table. See following examples. There is displayed table with two properties (table items) in one cell.
More values in one cell displayed in the navigator:
More values in one cell in the horizontal table:
More values in one cell displayed in standard vertical table :
More values in one cell displayed in vertical table with headers in one column:
Grouping of table items together is realized by selection of items in the navigator and then pressing button Indent.
All numerical values in tables can be also represented by background graph. The background graph can display relative value of current table field with respect to the maximal value of this field within the table.
The graphical representation of values can be switched ON / OFF in properties of the field. See the following picture, there is graphical representation of values switched ON for normal force (N) and shear force (Vy):
Since version 14.1 it is possible to overwrite the name of table cell (column). There is a property called Property name with the original name of the cell and property called Property user name in properties of the cells .
Empty value of property Property user name means that the original name will be used. Otherwise the value from this property will be used as a name of the cells.
User defined texts can contain the same formatting tags as can be used in the Formatted text (together with ampersand notation).
Since version 14.1 it is possible to change the horizontal alignment of values in tables. The property Horizontal alignment enables to switch between following modes:
The property Horizontal alignment affects only fields with values. The header of the table is always aligned to the centre.
In some cases there are very long texts in tables. Those texts can appear in header of table (names of values) or as the values itself. Those long texts can cause exceeding of tables (with automatic calculation of columns width) behind the page width. To prevent this exceeding it is possible (since version 2013.1) to switch ON wrapping of text in value fields and also in names of fields.
The first picture shows the table without text wrapping:
The second picture shows wrapping of long values:
And the third picture shows wrapping of long name of the value:
The text wrapping works for all possible modes of Width of cells evaluation (Fit to page width / User input / Automatic).
Because the text wrapping reduces speed of displaying of tables it is by default switched ON only in cases where the long texts are very common.
The text wrapping can be switched ON/OFF independently for each value in the table.
Since version 2013.1 it is possible to place pictures into tables. It is possible to decide independently for each picture whether is should be placed inside the table or outside.
Following types of table items can be inserted into a table:
Property - this type represents ordinary properties of elements.
Library reference - represents properties pointing to another project entity (e.g. reference to material, reference to cross section, reference to Layer, ...).
Sub-table - it is special table item which is used mainly in result tables. This table items contain another table. Layout of this table can be edited using "Edit "button.
Detailed output - it is special table item which is used mainly in detailed output of various checks. This table item can contain several texts and tables but is fixed and cannot be further edited.
Detailed output paragraph - it is similar to Detailed output but in this case it contains only part of the check (specific paragraph).
Variable type - it is type of table item without specifically defined type. It can contain pictures, texts, tables or combinations of them. This table item cannot be further edited.
Changing type - it is another variant of Variable type. In this case the type of one table items can change according to changes of result properties.
More complicated table items (Sub-table, Detailed output, Detailed output paragraph, Variable type and Changing type) are displayed bellow the main table:
The very first table layout for each entity is prepared by SCIA or by in-built automatic generator. User can modify this layout or create a new one.
New table layout can be created by typing a different text into combo-box with the name of table layout.
After the confirmation new table layout file is created in the USER\DocumentDefaults folder.
Each table layout is represented by one *.TLX file. Name of the file is composed from the identification of entity table and name of the layout.
EP_DSG_Elements.EP_StructNode [New name].TLX = "EP_DSG_Elements.EP_StructNode" (name of entity type) + "[New name]" (name of table layout) + ".TLX" (extension)
In the SCIA document UI there are displayed only names of the templates :
Set of predefined templates is stored in the installation directory of SCIA Engineer in the subdirectory \DocumentDefaults. Any further changes done in table templates are stored in USER\DocumentDefaults folder (the path to USER directory can be set in the setting in SCIA Engineer Setup / Options / Directories ).
In case there are templates with the same name in SCIA Engineer and USER directory the one from USER directory is used.
User should never change files with predefined templates in the SCIA Engineer directory.
If user needs to delete his template or return back to original state of templates it is possible to delete particular TLX file from USER\DocumentDefaults directory.
Sub-tables have their own TLX files with completely different name of file than is the name of TLX file of parent table.