Currently it is not possible to use wildcard expressions for Display Rules. Example: Override all attached files symbology (using a display rule) if the filename matches the following criteria:*DRA-100*.dgn - currentlythis does not work, onlya specific filename can be used which is not a flexible solution when you have a lot of files referenced (and potentially new files added in the future). Instead you have to explicitly type each file name eg. MEP-DRA-100-01-XRF-0001.dgn
Additionally, the option to choose the levels through predefined level filters would also be beneficial.
It looks like currently the wildcard can be used on some properties but not all (like for example levels). The example given in the this link clearly shows that the operator is set to "Like" and not "=". I believe that's why wildcard doesn't work on levels.
However I believe Level selection is one of the most useful cases of the wildcard, I'll give an example:
In ProStructures when creating rebar drawings the software automatically adds levels based on the original level the rebar is placed in. For example a 3D rebar element placed on level "PC_REBAR" will have a resymbolization in the 2D drawing on level "PC_Rebar_Level *" with "*" representing an enumerator. In this situation it's impossible to create seed files with the appropriate levels and level symbolization. So I'd rather work with display rules to adjust the symbolization (colour, line style, ...) based on the level name of the original 3D element.
Jan Šlegr 9 months ago
Even when I understand the reason of such enhancement, I am a bit worried about performance in this case. String comparison and analysis (required to implement wild card evaluation) is one from the most slow things in normal code, whereas I think display rules have to be as fast as possible.
Regards,
Jan
Edward Ashbolt 9 months ago in reply to Jan Šlegr
I can see you point, potentially it may become an issue running this on something like level names, where there are potentially many hundreds to compare. However that being said I feel the pros definitely outweigh the cons since it can be left to the end-user to decide whether or not it is worthwhile for their specific application of this type of expression. In most cases the performance difference would be negligible to the point of not even being noticed, especially for something like the reference name in the above example. I know I'd rather wait for half a second longer each time I opened a model, rather than manually enter a big list of file names and have to continually manage the list as each new file is added!