Hi
The custom configuration of the workspace environment which I am trying to develop does not pull libraries defined at the Organization-Civil level (no Feature Libraries, no Text Styles, no Levels).
I have basically followed the manual in the video and in the pdf document.
The folder with the standards inside the Organization-Civil folder is a copy of the original "_Civil Default Standards - Metric" folder and renamed to suit my needs. All stuff inside remains intact.
The .cfg file is renamed as shown above. The file content unchanged
The "Metric Standard" Workspace's config file contains the variable CIVIL_ORGANIZATION_NAME = SPI-Warszawa
# Do NOT include .cfg file extension in the variable definition. # <<<< Make Changes Here >>>> CIVIL_ORGANIZATION_NAME = SPI-Warszawa #------------------------------------------------------------------------------------
The configuration loads up without any error messages. Somehow the Organization-Civil level is ignored and only when it is renamed to something else than default -as delivered.
Here are debug files and config files. Can anyone have a look? plzzz
Debug.zip
OK, let's see what we've got...
At line 1017, the 1st major deviation occurs. In the file msdebug-DefaultLocation.txt is the line
Processing macro file [C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaceSetup.cfg]
but in the other msdebug, are the lines
Starting skip to endif, [C:\Program Files\Bentley\OpenRoads Designer CONNECT Edition\OpenRoadsDesigner\config\msconfig.cfg], line 267, depth = 0. endif, [C:\Program Files\Bentley\OpenRoads Designer CONNECT Edition\OpenRoadsDesigner\config\msconfig.cfg], line 269, depth = 0.
This appears to be related to line 1012 where _USTN_CUSTOM_CONFIGURATION is [(null)] in one file and [L:\Infra\Configuration\] in the other.
In the file where it is not null, _USTN_CONFIGURATION is then defined to the value of _USTN_CONFIGURATION.
The lines starting at 1017 show where a CFG file named WorkSpaceSetup.cfg is processed, or where it is not processed. The most likely reason is that in msconfig.cfg, it is trying to find any CFG file at the path defined by _USTN_CONFIGURATION. A quick check, in msconfig.cfg, using the line number (267) from the above snippet "Starting skip to endif, ..." shows that is indeed the case, except that is is actually looking specifically for a file named WorkSpaceSetup.cfg.
When you use the variable _USTN_CUSTOM_CONFIGURATION to redirect to the network, there must be a copy of WorkSpaceSetup.cfg at the location pointed to by _USTN_CUSTOM_CONFIGURATION.
Any major differences in the two files beyond this point is related to this missing file, for the most part.
I used Notepad++ with its Compare plugin to determine this. The other plugin I could not live without is its XML Tools plugin. That. and its User Define Language Syntax Highlighting tool. Next to Excel, its my most valued non-CAD program.
I hope this helps.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
Thank you for your time. After changing and testing over and over the ConfigurationSetup.cfg the cue to the weird result of the custom configuration is in line 26 of the ConfigurationSetup.cfg (see the code window below for the reference)
The line 26 normally in the file is not set (default as delivered) as in the documentation.
On the first run with only line 21 _USTN_CUSTOM_CONFIGURATION= set to the correct location and with the line 26 not set the ORD starts up with correct configuration. ALL works fine.
After closing the program the ConfigurationSetup.cfg in the line 26 is changed pointing to a location the same as my custom configuration. (it is all done automatically without me doing anything)
On the second run (me not touching anything) the custom wokspace of the Configuration\Organization-Civil does not load at all.
_____
On my other installation (other PC) the line 26 in ConfigurationSetup.cfg after first run points to the default location C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration although the custom configuration containing custom workspace is also set.
#---------------------------------------------------------------------- # ConfigurationSetup.cfg - Configures the root Configuration directory # for Your Organization # # The main function of this configuration file is to allow user to specify # the root Configuration directory to activate. The active Configuration # directory is represented by _USTN_CONFIGURATION. By default, it points to # the installed Configuration defined by _USTN_INSTALLED_CONFIGURATION, # which can consist of example WorkSpaces and WorkSets. # If your organization has its own Configuration directory, you can define # _USTN_CUSTOM_CONFIGURATION to that directory path and use it as follows. # #_USTN_CUSTOM_CONFIGURATION = D:/.../MyConfiguration/ #_USTN_CONFIGURATION : ${_USTN_CUSTOM_CONFIGURATION} #---------------------------------------------------------------------- #---------------------------------------------------------------------- # START: The section defines user selection at the time of installation. # These lines are generated by installer. [General] _USTN_CUSTOM_CONFIGURATION=C:\Users\Benek\Projekty\SPI-ORD-Configuration\ [SetConfiguration] %if !defined (_USTN_USER_CONFIGURATION) %if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION)) _USTN_CONFIGURATION = C:/Users/Benek/Projekty/SPI-ORD-Configuration/ %endif %endif