Software Directory
This section explains the various files and directories used by the 2D Rebar functionality. Understanding this is especially useful for initial configuration and setup.
- Library:
- REBAR_LIBDIR — defines the path for Rebar library.
- Project:
- REBAR_ PROJDIR — defines the path for 2D rebar detailing projects.
- REBAR_ PROJECT — defines the 2D rebar detailing project files. Required in ProjectWise Managed Workspace setups.
- REBAR_ PROJNAME — defined the name of the pre-selected 2D Rebar detailing project.
- Support:
- REBAR_ SIUPPDIR — defines the path for Rebar support files, and
- User:
- REBAR_ USERDIR — defines the Rebar application temporary directory for user.
C:\Program Files\Bentley\ProStructures CONNECT Edition\ProStructures\Default\appl
The Name of the pre-selected 2D Rebar detailing project, and
Project path are managed by WorkSpaces, e.g.:
C:\ProgramData\Bentley\ProStructures CONNECT Edition\...\WorkSpaces\<workspace>
Library
Several subdirectories are located in the Library directory. Each represents a separate storage area for the Object Files (dynamic reinforcement details) and associated GIF images created by 2D Rebar. The list of library directories varies from one version to the next. Examples of the Libraries found in your installation might be Beams, Bridge, Footings, Piers, and Walls. The software displays these library directories when you begin retrieving Objects. Objects created from your own drawings can be moved to these directories or any other library directories you may wish to create in the future. You are free to create your own Library directories. There is no limit to the number of subdirectories allowed.
Projects / Workspace
The Detailing sub-directory in the selected workspace contains the configuration files for your 2D Rebar Projects. Projects are normally configured for different clients, different design codes, and even perhaps for different detailing standards. Files are contained in each ..\Rebar\Detailing directory.
| display.sys |
Contains over 100 parameters controlling drafting standards used by Rebar during the detailing process. Parameters within this file, ranging from the length and angle of arrowheads to the color of label lines and patterning, can be changed at any time to suit your organization's established practices, or perhaps those of an external organization. |
| barmarks.sys | This text file is manually edited to modify 2D Rebar's bar shape designations for the current project. Standard shapes are included and excluded from the Rebar schedule library. Bar shape names/types can be altered. Default bend radius criteria can be overridden and bar shape dimensions can be renamed for each shape, e.g. dimension "A" renamed to dimension "F". |
| presets.sys | This text file is manually edited to establish a list of your preferred bar labels. The "Preset Text" entries in this file include all of your commonly-used bar labels or those of your Clients. Special codes are included in your Preset Text allowing 2D Rebar to dynamically update parameters such as bar diameter, bar mark number, shape codes, bar spacings, and many more. Bar labels are thereby automatically maintained whenever changes to your bar arrangements are made. |
| barchart.sys | The layout of your bar charts is controlled by commands within this text file. The name of Cell used as the basis for your chart is one of the first parameters specified. The location of the columns of bar data, the justification of the text, text heights, and colors and the inclusion of bar diagram cells for each bar are just some of the other controls available. |
| default.def | This binary file is created by the program during a detailing session. It contains a list of your preferred bar defaults which are read each time a new reinforcement drawing is created. The defaults are used as the starting values for all defaults used in your new drawings. This file cannot be modified with a Text Editor. |
Support
The..\Rebar\ support\ directory in system root path contains several more global configuration files.
- barcodes.sys: the design, detailing and scheduling data for all international design codes is stored in this file. Data is stored in a binary format. Therefore, the file cannot be edited using your normal text editor. Changes must be made interactively using the "Bar Codes" option within 2D Rebar's Settings menu.
- display.sys: with every new software release, more configuration parameters are usually added to the display.sys files within your Project directories. As an aid to upgrading your old display.sys files, a copy of the latest (most up-to-date) display.sys file is kept in your Support directory. During the startup process, the display.sys file in your Project directory is compared with the latest one in the Support directory. If new configuration parameters are found, your old display.sys file is upgraded, using the file within the support directory as the template for changes. Values for each parameter within the support directory file are always ignored. It is pointless to modify them in that file. Only the display.sys files in your Project directories should be modified.
- barmarks.sys: like the display.sys file (described above), the barmarks.sys file in the Support directory is used to upgrade old versions of the same file within each of your Project directories. This file contains a list of the latest available bar shapes. Again, the file should not be modified.
- Support / language directory: all international language files are located here, along with a special file called "startup" which contains the name of the language installed whenever a 2D Rebar session first commences.
- Support / barshape directory: contains a Cell library (shapes.cel) which includes a Cell diagram of each available bar shape. Also, within the directory is an image file (.gif or .png) for each available bar shape. These images are displayed by the software within the Schedule Listing dialog box and the Bar Shape Detector. While, you should avoid renaming or deleting any of these image files, they can be modified to suit your requirements.