Element Templates

Can some please explain why or how you uses the following in element templates

Levels you can have a primary level which seems to be the level the template will take when it is used, yet you can added multiply levels below this which dont seem to have any function at all.

This also seem to apply to all the attributes within  the templates including colour fill, hatching etc

many thanks

Mark

Parents
  • Mark, I am not sure that I follow you question, basically a template define properties of elements. this includes the level that the elements are placed on , color, style , weight etc. so when you pick your template this set that information for you so that when the element is placed it is placed with those attributes. does this help, if not can you provide more information on what you are trying to accomplish ?



  • Mark,
    Maybe a brief description on what you are looking to do may help. We can certainly explain what templates are and the options they have, but a workflow/steps/etc... of what you need will be more beneficial in helping us get you an answer.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Unknown said:
    If there are multiple instances of the same property and you do not want to use the default property, before drawing the element use the appropriate toolboxes to select “secondary” properties that match those in the template.

    It would be noted that there is no any dependency or linkage between active template and a selection of parameters implemented, so if multiple properties are defined in the template definition, it's not indicated anywhere and user is not aware of it. In my opinion it makes the whole concept of multiple elements pretty ineffective and hardly usable. The only tool which accepts and works with multiple properties is Standard Checker.

    With regards,

      Jan

  • Tim,
    I don't quite understand your explanation of how to select a different property in the element template. I have a single template set up with multiple levels, colors, and line weights. Can you explain further of how to select one of the secondary properties?

    Thanks.

    Rod Wing
    Senior Systems Analyst

  • Hi Rod,

    Unknown said:
    I don't quite understand your explanation of how to select a different property in the element template.

    As far as I know there is no such option. If there are e.g. 4 color defined in a template, still full color table is available ... which consequently means it's easy to select a color that doesn't conform to the template. But I am also curious if some trick exists.

    Regards,

      Jan

  • With OpenRoads transitioning to the use of Element Templates instead of xin file preferences I can see how this would be useful for specifying different display properties for plan view vs. profile view, etc. I'm just curious on how you can use this in standard MicroStation.

    Rod Wing
    Senior Systems Analyst

  • It is what Jan has stated. There is no "multiple choice". If a template is selected and you have only set one choice for all the settings, then it sets these as the "active" settings for the element placement. The user can still choose another setting, it does not stop them from doing this, it only gives them a "default" setting so they do not need to choose or remember what it is supposed to be. Templates do not keep users from picking different options, it only sets a default so the user does not HAVE to choose. Now - going forward if you want to check elements to see if they are "following" a template, then the element can be associated with the template and you can run standards checker to flag anything not following the template. They may be an instance where a template may fit several scenarios where more than one color will still work for the template. This is where you would add these additional settings. Although the template itself when selected can only set one color (its default) there are several others colors that will still fit into the requirements. So if the user chooses one of the other colors, when standards checker is run, these elements would pass because one of the colors selected is in the list. It doesn't limit the users choices of colors that they can pick, it only limits what will pass when the template is used by standards checker against the element.

    An example would be if I created a template that had 3 colors in it (lets say green, blue and red). The default color is red. I choose the template and it sets my color to red. It does not prevent me from choosing another color and it does not limit my choices to only 3 colors. I can choose what I want, but it defaulted to red. Lets say I pick orange for the color. I run standards checker and it scans the element with the template provided. As long as the element is red, green or blue, it would pass, but since it is not, it would be flagged.

    I hope this makes sense.
    Let me know.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

Reply
  • It is what Jan has stated. There is no "multiple choice". If a template is selected and you have only set one choice for all the settings, then it sets these as the "active" settings for the element placement. The user can still choose another setting, it does not stop them from doing this, it only gives them a "default" setting so they do not need to choose or remember what it is supposed to be. Templates do not keep users from picking different options, it only sets a default so the user does not HAVE to choose. Now - going forward if you want to check elements to see if they are "following" a template, then the element can be associated with the template and you can run standards checker to flag anything not following the template. They may be an instance where a template may fit several scenarios where more than one color will still work for the template. This is where you would add these additional settings. Although the template itself when selected can only set one color (its default) there are several others colors that will still fit into the requirements. So if the user chooses one of the other colors, when standards checker is run, these elements would pass because one of the colors selected is in the list. It doesn't limit the users choices of colors that they can pick, it only limits what will pass when the template is used by standards checker against the element.

    An example would be if I created a template that had 3 colors in it (lets say green, blue and red). The default color is red. I choose the template and it sets my color to red. It does not prevent me from choosing another color and it does not limit my choices to only 3 colors. I can choose what I want, but it defaulted to red. Lets say I pick orange for the color. I run standards checker and it scans the element with the template provided. As long as the element is red, green or blue, it would pass, but since it is not, it would be flagged.

    I hope this makes sense.
    Let me know.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

Children