Manual

InBlocks

Introduction.............................................................................................................................................. 3 InBlock definition .............................................................................................................................. 3 InBlock instance ................................................................................................................................ 3 Schema ............................................................................................................................................... 4 Types of InBlocks .................................................................................................................................... 5 Hardcoded .......................................................................................................................................... 5 InBlocks stored in DB4 files ............................................................................................................. 5 Catalogue InBlocks ........................................................................................................................... 6 Template InBlocks............................................................................................................................. 7 Inserting of InBlocks into project .......................................................................................................... 8 Manipulations with InBlock instances .................................................................................................. 9 Instance manager .............................................................................................................................. 9 Changes in InBlock definition .............................................................................................................. 10 Common setting of InBlock definition ................................................................................................ 11 Protection of InBlock ...................................................................................................................... 11 Statuses of InBlock definition ........................................................................................................ 11 Definition document........................................................................................................................ 13 Drawing style ................................................................................................................................... 14 Explanation picture and icon ......................................................................................................... 15 Updates of InBlocks .............................................................................................................................. 16 Document & XML ................................................................................................................................... 17

Introduction
The InBlock is new special object in Scia Engineer. It stores a separate project (part of structure) and can insert or update instances of this project in the main project. There are InBlock definitions and InBlock instances in the project.

InBlock definition
InBlock definition contains the internal Data Server (DS) with a part of the model. In the properties of InBlock definition parameters of the project stored in InBlock DS are defined together with other properties which are common to all InBlock definitions. For description of definition properties will be given in following chapters.

InBlock instance
InBlock instances are defined by insertion point (or more points in case of multiple instances) and by the reference to the InBlock definition. There is also a link between the instances and the basic Scia Engineer-members belonging to the instance. On instances an update action which changes linked Scia Engineer-members linked to the definition according to status of project stored in DS of InBlock definition can be applied. There are two types of InBlock instances available: - instance on single vertex with LCS - instance on repeated vertexes with LCS

Instance on single vertex

In the properties of instance on single vertex is: - Insertion point where in the project is placed the instance - Axes (X,Y,Z) defining the orientation of instance LCS - Rotation of instance with respect to GCS (changes of rotation will recalculate axes) - Zero point offset in GCS from insertion point

Instance on repeated vertexes

Properties of instance on repeated vertex contain: - Insertion point where the first vertex is inserted in the main project - Axes (X,Y,Z), Rotation rotation of each instance with respect to GCS - Zero point offset in GCS of each instance from its insertion point - Count the number of instances which will be generated - Offset (X,Y,Z) distance between instances in X(Y,Z) directions - Rotation rotation increment between instances

Schema

Types of InBlocks Hardcoded

Hardcoded InBlocks are specially developed InBlocks by SCIA developers.

InBlocks stored in DB4 files

Manager of InBlock definitions is a standard library manager and therefore all information stored in this manager can be stored in the DB4 file. Special for InBlock is that in case of existing DB4 file, the content of this file is visible in the tree in the dialog for inserting of new InBlocks:

There is a list of properties with values, icon and static picture as a preview of the InBlock. This type of InBlock enables storing of all properties of InBlock definition (i.e. protection, definition document, icon, explanation picture and style of instance update). This is the only way how to use one user-made InBlock in several project with all necessary settings.
Note:

When a Template InBlocks is stored to DB4, then it stores the path to the template file. When sending this DB4 to another user (another machine) you need to send also the file and modify the path on second machine. DB4 file with InBlock definitions must be placed in User directory and must be named EP_StructuralBlock.db4 to be visible in the tree.

Catalogue InBlocks
This type of InBlock enables the user to insert a regular Catalague block as an InBlock. It means that it is possible to change parameters of this catalogue block lately, when it is already inserted into project. The whole list of all catalogue blocks is available.

In the properties of catalogue InBlocks definition there are parameters from the catalogue block. Also the geometry editor of the Ctalogue block is available. It is accessible via button Catalogue block editor.

Note:

Catalogue blocks are independent on national code and can be inserted to any project with any national code.

Template InBlocks
Any project stored in User block libraries directory can be inserted as a template InBlock. If there are subdirectiories, then they are displayed as tree in the list of available InBlocks.

The user Template InBlock definitions and subsequently instances can be modified via button Edit template parameters or Catalogue browser from properties of InBlock definition.

Note:

In the properties of the definition there is also the filename with the path. It enables the user to change the template file, but this must be considered when using a project with such InBlock on more than one computer. The project which already contains an InBlock definition cannot be inserted as a template InBlock (nested InBlocks are not supported)

Inserting InBlocks to project

There is a special group in service Structure called Advanced input.

When the user inserts a new InBlock to a project he can select from the list of available InBlocks. The list is tree-sorted by types. Filtering of the list is available.

When the user launches New InBlock then he can select from all available types. If he launches New catalogue InBlock or New user InBlock then the list is filtered and only relevant InBlocks are displayed. When user selects some type then it is stored to the library manager with definitions. From this library manager it is possible to insert instances to the project (Insert existing InBlock).

Manipulations with InBlock instances

InBlock instances can be manipulated using standard geometrical manipulations. Note that geometrical manipulations (also rotation or mirroring) modify only position of inserting nodes. It means that rotation of InBlock instance can be modified only via changes in properties of InBlock instance (see chapter about Instances and description of their properties). Other way how to modify and add instances is Instance manager:

Instance manager
Instance manager is accessible via the action button in the properties of an InBlock definition.

It lists all instances from the definition. Here it is possible to do all standard library operations: (New instance, edit instance, copy instance, delete, undo, redo) In addition, there are available special functions related to instances only: (Deep update, standard update, disconnect link between instance and generated objects, remove objects generated by the instance from main project).

Changes in InBlock definition

InBlock definition can be modified by properties of InBlock definition or by template or user block editors accessible via buttons in InBlock definition properties. Those changes are not applied instantly to the DS in the definition. They are applied on demand after pressing action button Update definition. This action button appears after any changes in parameters related to InBlock definition DS. Available is also button Regenerate InBlock definition and Instances. This button updates definition DS and updates all instances belonging to this definition.

10

Common setting of InBlock definition

In the properties of all types of InBlock definitions common groups with properties are available: - Basic setting (document, protection), - Setup (drawing, pictures, setting for update).

Protection of InBlock
Two types of InBlock protection are available: (for setup of the protection see next chapter) - protection of administration - protection of using The user of an InBlock with protected administration can modify drawing style, outside changes and style of instance update only. Changing the definition of the document, explanation picture, icon and protection is protected by administrator password. Working with instances is not limited (protected). Modification of InBlock parameters is allowed. In fact the modification of parameters is allowed but the update of definition is protected so unauthorized user cannot change anything in the InBlock. Instances can be freely inserted to the project, updated, etc The user InBlock with protected using has the same restrictions as the ones with protected administration. In addition modification of InBlock parameters (update of definition) is protected by password or other means of protection (see chapter about Protected InBlock in administrator mode).

Statuses of InBlock definition

InBlock can have three different statuses related to the protection of the InBlock. Properties are displayed according to current status: 1. Unprotected InBlock (see screenshot in chapter Common setting 2. Protected InBlock user mode 3. Protected InBlock administrator mode

11

InBlock without protection

This is the basic mode (status) of InBlock. Using of the InBlock is not limited. Any user can use it without any restrictions. All properties are available. It is possible to Enable block protection. When the user clicks on this button, he is asked to enter the new administrator password (at least 5 characters). After entering new password, the InBlock becomes protected and properties are switched to Administrator mode.

Protected InBlock administrator mode

In the Administrator mode it is possible to modify all settings of InBlock and in addition the details about InBlock protection. User (administrator) can change administrator password or remove InBlock protection at all. User (administrator) can also change the protection of the InBlock. There are available two types of this protection: 1. by COM object (simple COM object created by the user (administrator) and identified by its CLSID. The evaluation of protection implemented in COM is arbitrary. The intention is that it will use Scia Engineer defender and check commercial modules. 2. by password

Protected InBlock user mode

In the user mode it is not allowed to modify the protection setting. It is also not available to change the explanation picture or icon. Also the definition document template cannot be changed. When the user wants to switch to the Administrator mode he is asked for the administrator password.

12

Definition document
The definition document can present data from Data Server of InBlock definition. It can display all entities in the definition. The position of nodes in coordinate system of project stored in definition DS. The definition document can be assigned by selection of a standard document template. Then it can be previewed using action button in the properties of the definition. Once the document template is assigned, it is marked in properties and button for removing appears. Also an action button for preview is available once the template is assigned.

13

Drawing style
Two drawing styles are available in the properties of InBlock definition: 1. Bounding box 2. Mark (cross in insertion point)

The picture shows the Portal Frame InBlocks displayed with Bounding box. The Wall InBlocks are displayed using the Mark option.

14

Explanation picture and icon

The explanation picture and icon cannot be modified in the User mode. This picture and icon are visible when a new InBlock definition is being inserted from a DB4 file.

Explanation picture is a static picture (wmf, bmp, gif, jpg).

15

Updates of InBlocks
Two update styles are available: 1. Standard 2. Deep The user can modify the style of update in properties of InBlock definition.

Standard update
Standard update: this update works the same as the ESA-ESA update. It compares the properties of old and new objects and modifies only the different ones. The standard update is intended to keep the lately added add-data but development of this should still be finished. In some cases standard update produce incorrect shape of structure.

Deep update
Deep update: this update deletes existing entities which were generated by the InBlock instance and creates them newly. Add-data which were added on those entities are lost after deep update. Deep update always produce correct shape of structure. When Update on manipulations is checked, then after each manipulation with instance (move, rotate, etc...) is automatically started update of this instance. Otherwise the update must be started manually from instance action button.

Update of all instances related to some definition can be also launched from action button Deep update for all instances from properties of definition.

16

Document & XML

InBlocks cannot be used in document or XML yet.

17