Quantcast
Channel: OpenRoads | OpenSite Forum - Recent Threads
Viewing all articles
Browse latest Browse all 15087

Geopak/InRoads [OR] Civil_XIN_FILE configuration question

$
0
0

The following questions apply to Geopak and InRoads versions 08.11.09.878 (ss4)

Appears that Geopak SS4 and InRoads ss4 use the "CIVIL_XIN_FILE" configuration to specify the file that is used for applying certain Preferences.  A good example is when using the "Create Cross Section" tool, we can pick the Preferences which loads preset information.  In InRoads ss2 the xin file had a corresponding lock file that would allow everyone to *USE* the xin, but only one person could make changes at any time.  Anyone with "read only" permission wouldn't be able to use the Preference "Save" button because it would be grayed out (thus unavailable).  But, they could use previously created preferences.

Question1:  Why isn't this configuration documented in the OpenRoads help?  Or, am I just blind and not seeing it...

For Geopak ss4:

On many projects people will likely point to the same XIN file for consistency.  How does this file control who can make changes if multiple people have it open and are making changes throughout the day?  Geopak doesn't seem to be creating a corresponding lock file when the xin is opened.

For InRoads ss4:

Inroads does indeed seem to continue to create a lock file when the xin file is opened using the "CIVIL_XIN_FILE" configuration.  The problem is that it doesn't seem to control who's allowed to make changes.  I just did a quick test with another user and both of us were permitted to make changes to the same file on the server (despite the ss2 dialog showing me as read/write and him as read only).  But, whomever closed Microstation last was the only person whose changes were actually saved.   Can anyone shed light on this?   Seems like the safe bet for InRoads is to use Project Default or rwk to define the xin (not the config).

thanks,

Mark


Viewing all articles
Browse latest Browse all 15087

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>