CIVIL_XIN_FILE configuration

RE: CIVIL_XIN_FILE configuration

Katie Johnson — Wed, 02 Aug 2017 15:29:03 GMT

Thank you -will try it!

RE: CIVIL_XIN_FILE configuration

Kevin McDonald — Wed, 02 Aug 2017 15:23:25 GMT

If they can not see any preferences in the list, it is most likely this: https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/31445/xin-is-blank---preferences-and-styles-lists-are-empty

RE: CIVIL_XIN_FILE configuration

Katie Johnson — Wed, 02 Aug 2017 15:19:19 GMT

I am having a perhaps similar issue: I notice that, although the path in the variable definition remains the same, the source of the configuration variable changes from "Project" when PowerGEOPAK is first started, to "User" as soon as I invoke the Create Cross Section tool. This variable does not get stored into the User Configuration File, however.

But the issue I am having, which may or may not be related, is that for only some of the PowerGEOPAK users at one client, they cannot access the create cross section or the annotate cross section preferences that are stored in the xin file. Nor do they have the option to Save new preferences as the Save button is ghosted.

We have checked the config files for typos, and moved the file around and changed names etc. to help to make sure that we were not missing a typo, but since some users can actually see the preferences from the xin file, I think that the variable expands to the correct location.

Any thoughts on what to try next?

RE: CIVIL_XIN_FILE configuration

Derek Schmidt — Tue, 04 Oct 2016 13:35:33 GMT

Judging from the write-up of your problem, it sounded to me like the file Microstation was reading wasn't the file you (or your workspace manager) were expecting. In light of that, it was worth working out exactly where the value of CIVIL_XIN_FILE is being defined.

Looking at it, I see that in line 808 CIVIL_XIN_FILE is defined at the application level.

In line 981, it is defined at the user level, and (in this case) at line 975 you have the name of the file that defines it.

At line 1365, the final value is reported. Of course CIVIL_XIN_FILE hadn't been redefined since then, so it's the same as the definition from line 981.

The only thing I was suggesting to look at is that final value, to confirm that it is the right file that you expect it to be. I hope that helps, though I don't necessarily expect it to. Beyond that, I can't help on this.

Edit: Having re-read your problem, it sounds like this may indeed be part of a workaround without necessarily being a solution. (When you redefine a variable, it should be saved, but apparently it's not. Therefore, you need a workaround.) Locating exactly where CIVIL_XIN_FILE is defined, you will be able to define it to whatever it needs to be in the source file where it is defined now.

RE: CIVIL_XIN_FILE configuration

Paweł Szabłowski — Tue, 04 Oct 2016 07:10:44 GMT

Derek, I got debug report. what's next?

communities.bentley.com/.../6036.msdebug.txt

RE: CIVIL_XIN_FILE configuration

Paweł Szabłowski — Tue, 04 Oct 2016 06:54:00 GMT

Kevin could you elaborate on this using an example?
It was set: CIVIL_XIN_FILE and Project Default. and nothing better.

RE: CIVIL_XIN_FILE configuration

Derek Schmidt — Tue, 27 Sep 2016 13:58:03 GMT

Consider adding -debug to the end of the command line that you use to open PowerCivil. This will create a file, the path to which is provided in the last line after loading everything. Open that file. Look for all instances of CIVIL_XIN_FILE to see how it is specified.

That should reveal to you how that variable is set, and should get you closer to finding out why it might be reset.

RE: CIVIL_XIN_FILE configuration

Kevin McDonald — Tue, 27 Sep 2016 13:12:34 GMT

For InRoads and Power Civil users, this is still set in File>Project Defaults>Preferences (*.XIN). The value set there is then set for the CIVIL_XIN_FILE variable at the user level.