Hi,
We use references with configuration variables to define the path for every project we have. (Standard details that are used on each project.)
In Microstation 7, when you double clicked a file (with the path defined by a configuration variable) in the Reference File dialog box, and then hit browse, it would take you to the folder that is defined by the configuration variable. You could select a new file and it would keep the configuration variable associated with it, unless you were to change folders.
In Microstation 8 and Microstation Connect, this feature was lost. Now if you double click the reference file and hit browse, it will take you to the folder defined by the configuration variable. If you select a new file, or even just hit "open" without selecting a new file, the configuration variable is lost and there is no warning. (The only way it will find the file is through the hidden saved full path, which is NOT good!)
Please add this feature back into Microstation. You should not loose the configuration variable definition just by saying "o.k." I tried to file this as a service request (SrvReqNo:[7000830716]), but the response was, "I have found a defect that was filed for V8i on the same issue, however Development has determined that this is working as designed. So Connect it would be working as designed as well. the defect number was 37219". Please fix this again.
--Thanks,--Robert Arnold
Microstation 7:
[View:/cfs-file/__key/telligent-ideas/d5d6c2ef-925b-4a51-8509-a07c253d4226/1121.Mstn-v7.mp4:480:360]
Microstation Connect Update 10:
[View:~/cfs-file/__key/telligent-ideas/d5d6c2ef-925b-4a51-8509-a07c253d4226/Mstn-Connect.mp4:640:480]
Hi,
I just had to help a co-worker with this. She is reattaching files from a folder defined by a configuration variable. In this case, the folder is defined by the variable "Details 23". She double clicked on "Details23:ThisFile.dgn", then was directed to the correct folder, selected "ThatFile.dgn" and had the result of "ThatFile.dgn" without the "Details23:" part of the name. The file showed up correctly on her screen, so she didn't notice that her reference was relying on the full path to find it, instead of the configuration variable path.
If Bentley is so against using the full path, then why does reattaching a file based on the configuration variable path, default to using the full path?
FYI, every project we have (except a very few) relies on configuration variables for most of the details.
--Thanks,
--Robert Arnold