2020 Table of Contents

Updates in Template Editor, template handling and reports

Last updated March 10, 2020 by Tekla User Assistance tekla.documentation@trimble.com

Software version: 
2020

Updates in Template Editor, template handling and reports

Updates in Template Editor, template handling and reports

Template Editor 4.0.xxxxx release notes

Note:

Files saved with Template Editortool in Tekla Structures that is used for creating and modifying templates to be used in drawings and reports

4.0 cannot be opened with older Template Editor versions due to new features in version 4.0. So template definition files (.tpl and .rpt files) have now a new version number 400 (previous was 360).

For more information about Template Editor 4.0, see Template Editor 4.0 User's Guide.

  • Updated the latest help files.

  • Multiline value field should have its content attached to the top, so the data is filled from top to bottom. Default will remain from bottom so as not to break old behavior.

  • Template objectentity in a template component that is used to add either graphical or textual data

    The template type determines what kinds of template objects can appear inside its template components. Template objects can be basic geometric shapes, text objects, symbols, bitmaps, imported files, or field objects.

    Template objects are represented as rows in the template components.

    colors can now be overridden in row rules by defining an override parameter for the Output() function. For more information, see “Overriding template object colors with row rules in Template” in Template Editor 4.0 User's Guide.

    The following rule overrides the colors when the LENGTH attribute is longer than 1000. Value fields are orange, text objects are yellow and the drawing color is blue (i.e. lines are blue).

    Choose from the 14 colors that you can use in Template Editor. Valid color names are black, white, red, green, blue, cyan, yellow, magenta, brown, darkgreen, navyblue, greenblue, orange and gray. The color names are case-insensitive.

  • Added automatic font resize for a value field when the content exceeds the defined length of the value field.

Template handing - dkit 4.0.xxxxx release notes

  • Reduced memory usage during template output by using dynamic allocation for components.

  • Template width was spread according to the total text length in a multi-line text object, because line breaks were ignored when the length was calculated. This has now been fixed.

  • The performance is now better for large templates.

  • Reduced memory usage during template output (pooling for objects and more precise allocation of object identifiers).

  • The template height calculation was wrong when template used a table with horizontal fill direction and a variable number of columns. This has now been fixed.

  • Multiline value field should have its content attached to the top, so the data is filled from top to bottom. Default will remain from bottom so as not to break old behavior.

  • Tekla Structures crashed when a drawing had a pull-outsmall graphic in a reinforcement mark, table, or report template that shows the shape and dimensions of a reinforcing bar

    rebar meshreinforcement that represents a mesh of steel bars in two perpendicular directions

    In Tekla Structures, the reinforcement mesh bars in one direction are called main bars and reinforcement mesh bars perpendicular to them are called crossing bars.

    . This has now been fixed.

  • PageBreak() function in a row was creating an extra page if it was used after a table. This has now been fixed.

  • Two different cases exist for header and footer output:

    1) If rows don't have rules, then headers and footers)are always output.

    2) If at least one row has a rule, then if no rows are output, the headers and footers will not be output either.

  • Template object colors can now be overridden in row rules by defining an override parameter for the Output() function.

  • Added automatic font resize for a value field when the content exceeds the defined length of the value field.

New content type HIERARCHIC_CAST_UNIT in Template Editor

  • Template Editor contains a new content typedetermination of which template attributes can be used in the template object value fields for a template component row

    Content types are mainly based on object types.

    HIERARCHIC_CAST_UNIT for reporting. Now you can create reports listing subassemblies of concrete.

    The content type CAST_UNIT is flat, contrary to the steel ASSEMBLY. The new content type, HIERARCHIC_CAST_UNIT, supports hierarchy with the same logic as ASSEMBLY. It enables reports that list the hierarchic content of cast units with multiple levels of subassemblies, for example, double walls. The existing CAST_UNIT has not been changed.

Other Template Editor updates

  • Numbers that exceed the length field of a template are now correctly truncated with * symbols.

  • Modifying a report in Template Editor was very slow. This has now been fixed and the performance of Template Editor has been improved.

Quick feedback

The feedback you give here is not visible to other users. We use your comments to improve our content.
We use this to prevent automated spam submissions.
Content rating: 
No votes yet