Allow the Civil Stroke Settings to be stamped into the corridor read/write instead of read-only and read from the configuration.
Some corridors require tighter tolerances than others. For instance, a ditch or end condition corridor does not need the same tolerance as a pavement surface.
If a Corridor file is opened in a different workspace where the configuration is different the model will change. As an "owner" we send and receive files from consultants and contractors constantly. If someone were to unintentionally open the file with "no workspace" "no workset" the results of the engineering components should be the same.
**The response by the Admin to "NEVER" open in a different workspace highlights the issues with the software. Any workspace setting that manipulates or modifies a files design intent by opening it should not exist.
I respectfully disagree with your assessment that the point of the workspace is to govern setting dgn settings throughout a project lifecycle.
“Many of life’s failures are people who did not realize how close they were to success when they gave up.” —Thomas Edison
| Civil Product Used | OpenRoads Designer |
It is recommended to NEVER open a corridor model in another workspace. Stroking settings would be the least of your concerns. You risk issues with units, Feature Definitions, Element Templates, Levels, Item Types, etc.
Reference the corridor in if it needs to be viewed. It should only be opened in the workspace that was used to build it.
The software is functioning as intended. It has been designed to use workspaces to control the settings for different worksets and dgns. This is a longstanding feature that has been in place for decades.