Custom configuration variable creation

Mark Plum said:

MS_DEF

MicroStation configuration variables have the prefix MS_.  That enables you to distinguish them from your custom configuration variables.

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.

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)?

I think there is a misconception as to what these variables control or how they function. Yes a default is provided, but most assume that this is what holds and it as to how it will always open to. I believe there are several situations here, each to do with these various dialogs. 

I don't think it is a question of where it starts, but more along the lines of where it can be pointed permanently. In other words, they don't care where they browsed last, they want it to always open at one location, no matter what.

and this is not how it currently functions.

Tim, PRECISELY! Practically every single user (ADMIN)  I have spoken with through many different companies would like to have a structure by which the current options are available to the end users and also "fixed" directories where information may always be found. Bentley has attempted to fix this situation through a "Standards directory" (V8i) and now an "Organization" directory (CONNECT), it seems, but such does not exactly "remedy" this long standing situation.

And yes, John, you understand the situation well.

the intent of those directories was not an attempt to fix this issue.

Tim: Yeah, no doubt. Nonetheless, the issue still exists... I actually like the new structure within CONNECT although it has taken a bit willpower to embrace it. 

Tim: Yeah, no doubt. Nonetheless, the issue still exists... I actually like the new structure within CONNECT although it has taken a bit willpower to embrace it.