Parameter codes for the Desc. Key Manager

[yusefk]

My problem is a little difficult to explain so I'll just cite an example.

 

Right now I have CO* for cleanout and COL* for column as my description keys. However, if the description is COL the DKM still recognizes it as CO. I understand why it's doing this however, I'm looking for a strategy to remedy this. There are several other instances where this is a problem so a global way to do this would be appreciated.

[Cad64]

Uh . . . . I think this is a Land Desktop question? Posting in the 3DS Max section won't do you much good. I have moved your question to the "Civil 3D and LDD" section.

[rustysilo]

The only thing I know of is to come up with different desc keys for those instances, or create different desc key sets and import the points separately.

 

What do the wildcard characters (ie - *) represent in the description of those particular points?

[yusefk]

Yeah we're trying to avoid having to make the guys in the field change what they save points as (apparently it's too complicated ;P). As far as wildcard, CO needs to match any number, letter, or string after it as it can be used in many different situations. I'm hoping there's a way to write a script that uses a decision structure to test for 'L' after the CO and ignore the rest.

[rustysilo]

Sorry. I have no idea if that can be done.