I am attempting to create custom configuration variables in order for the workset configuration file to find a directory path defined by the variables (similar to defining MS_DEF to point to a particular directory for finding dgn files). In particular, I am attempting to have two custom variables (MS_POINTCLOUDDIR and MS_REALITYMESHDIR) located within the workset.cfg file point to directories when one executes Point Cloud> Attach and Reality Mesh> Attach. Any idea how I may get this concept to work? Am I merely missing configuration variables which already exist (as they exist for attaching dgns, refs, and images)?
Thanks!
Mark
Mark Plum said:MS_DEF
MicroStation configuration variables have the prefix MS_. That enables you to distinguish them from your custom configuration variables.
MS_
Mark Plum said:I am attempting to have two custom variables (MS_POINTCLOUDDIR and MS_REALITYMESHDIR)
You've created a maintenance problem. How will you distinguish your variables from MicroStation's variables in, say, a year's time? Choose a distinct prefix that means something to your project or organisation. For example, since your organisation is Poe and P Associates, why not PP_POINTCLOUDDIR and PP_REALITYMESHDIR.
PP_POINTCLOUDDIR
PP_REALITYMESHDIR
Regards, Jon Summers LA Solutions
OK, no problem with the change of syntax of course (and I understand your point). Still, let me change those variables to PP_POINTCLOUDDIR and PP_REALITYMESHDIR and point those to a particular directory. How do I get Point Cloud> Attach and Reality Mesh> Attach to default to that (those) directory(s) at the workset level? Also, what happened to runmacro.ma (it does not seem to be included with Connect (or has not been updated to this latest edition of MicroStation)?
Is there a starting point variable for all the windows open dialogs? I would think that would be a start to allow the admin control. These two dialogs don't seem to have them. If the 90% use case is always attach from this location then a variable to start them in that location would be helpful. Also things like these would 90% of the time be in a folder or two within a project and the user wouldn't navigate far from the base folder but something like a reference could be all over the project in different discipline folders etc. Maybe its not an all approach as you suggest, but I do like consistency as then the user knows what to expect every time.
~HTH
John.
yep
I suppose that my end result would be to create two variables (like MS_REF_DEFAULTATTACHDIRECTORY) for Point clouds and reality meshes. If users find use in them, so be it. If users do not decide to use them, so be it. We would like to have them here. Heck, throw one in for images as well and we would be completely satisfied. From a workflow perspective, the ribbon clearly states Attach Tools > References, Raster Manager, Point Clouds, and Reality Mesh. Why not make all variables consistent across that range?Again, admins are under no obligation to use such variables, but it would be nice to have them.
And yes, John, you have expressed my point quite succinctly.
Mark, I'd suggest you file an enhancement request on these items. It will require a request for each item individually.
I have never performed such a request, John. Could you lead me in direction?
Open CONNECTION Client and click on the CONNECTION Center, in the browser on the Bentley Cloud Services page at the bottom click on the "New Service Request". Should be self explanatory from there.
Thank you so much, John. Requests have been made and email confirmations have been received! Have a great rest of your week!