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)?
I actually did create a comment line within the workset cfg fileto state #Poe Custom Configuration Variables (to answer your question on distinguishing these variables (your idea of PP_ is better, I think).
Mark Plum said: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)?
It's no longer necessary with CONNECT. You can instruct a VBA macro to start automatically without external code. See VBA help.
Post questions about VBA to the MicroStation Programming Forum.
Wow, well how neat is that (about the ma/ macro), Jon! Excellent!