Colorizer

Colorizer

Summary

Colorizer allows users to create element filters to set and/or clear element colors in select views based on user-defined conditions.

  • eVolve tab ⮞ Utilities panel ⮞ Colorizer button

Prerequisites

Usage

Creating a Colorizer rule

  1. From the EVOLVE ribbon, in the Utilities menu, click Colorizer.
  2. From the Colorizer window, in the grid, select a cell from the Click here to add a new row and specify the following:

Required

  • Rule Name - the name does not have to be unique as you may utilize Description, Group, and Sub Group to further distinguish it from other profiles.
  • Element Filter - defines the elements the colorizer rule will color.
  • View Filter - when defining the View Filter, select the Views category and any optional conditions the view(s) must adhere to run the colorizer rule.

Optional

  • Run Order - automatically assigned if undefined.
  • Description - blank if left undefined.
  • Group - blank if left undefined.
  • Sub Group - blank if left undefined.
  • Enabled - the default state is unchecked; remember to check this option or the rule will not run.
  • Execute On - the default value is Manual Only if left undefined.
  • Run in Second Pass - the default state is checked.
  • Process Nested Elements - the default state is checked.
  • Allow Multiple Processing - the default state is checked.
  • Background Color - the default values are RGB 0,0,0 / HSB 0,0,0 / HEX #000000 if left undefined.
    • While a no-color value(like the default value) may be the desired result, remember to define a color if the rule intends to color an element.
  • Background Pattern -the default value is [EditValue is null] if left undefined.
    • Typically set to <Solid fill>, especially when using a Foreground Color and Pattern, even when the rule is "enabled" if a value for either the Foreground Pattern and/or Background Pattern is not set, it will appear as if the rule is disabled.
  • Foreground Color - the default values are RGB 0,0,0 / HSB 0,0,0 / HEX #000000 if left undefined.
    • If the Foreground Pattern is not defined, the Foreground Color is not applied.
  • Foreground Pattern - the default value is [EditValue is null] if left undefined.
    • Typically set to a pattern other than <Solid fill>, especially when using a solid Background.
  • Clear Colorizer - the default state is unchecked.
  1. After the Required and Optional fields are defined, click Apply. The new row is added to the grid.

Window Overview

Tool Palette buttons
  • Refresh Current View - used to re-run the selected rules on the current active view.
  • Refresh Full Project - used to re-run the selected rules on the entire project view.
  • Export Rules (Removed as of 6.2)- used to transfer the selected rules to another project.
  • Import Rules (Deprecated as of v6.2) - used to bring in rules from another project.

  • Configuration Exchange - Used to import/export rules; please see the Configuration Exchange article for more information.
Grid Columns
  • Run Order - used to define the sequence in which the rules are executed, 1 is 1st, 2 is 2nd, 3 is 3rd, etc.
  • Rule Name - used to apply a label to a rule.
  • Description - used to provide additional information about the rule.
  • Group - used to assign a category/type to a rule.
  • Sub Group - used to a subset of a group/category to a rule.
  • Element Filter - used to define the categories and optional conditions which elements and their parameters are filtered against.
  • View Filter - an embedded selection filter that defines optional conditions for the View(s) that the rule runs against.
  • Enabled - if unchecked, the rule is disabled and will not run.
  • Execute On - defined when/how the rule runs.
    • Manual Only - the rule will only run when either the Refresh Current View or Refresh Full Project button is manually clicked.
    • Any Update - the rule runs when any change to the drawing is made.
    • New Element Creation - the rule will only run when an element is placed on the drawing area.
    • Existing Element Change - the rule runs when an existing element is modified.
  • Run in Second Pass - indicates whether the rule runs after all other processing has been completed; see below for more information.
  • Process Nested Elements - when checked, nested elements are colored.
  • Allow Multiple Processing - gets or sets a value indicating whether multiple processing of the same element is allowed in a single execution session; see below for more information.
  • Foreground Color - a color picker used to define the color of the surface foreground, cut foreground, and line color.
  • Foreground Pattern - defines the pattern used when applying the foreground color to the surface and the cut foreground.
  • Background Color - a color picker used to define the color of the surface and the cut background.
  • Background Pattern - defines the pattern used when applying the background color to the surface and the cut background.
  • Clear Colorizer - a checkbox used to indicate whether or not the rule is used to clear the graphics override settings applied by the Colorizer rule instead of setting them.
Record Navigator buttons
  • Add - used to add a new row to the grid.
  • Delete - used to delete selected row(s).
  • Duplicate - used to duplicate selected rows.
  • Export Grid - exports the grid as currently displayed to Excel.
  • Bulk Update - allows for the values in multiple selected rows to be revised at once.

Tips and Tricks

  • To revert the Color and/or Pattern to their default state, click the desired cell, then press Ctrl + Del

Run in Second Pass

The Run in Second Pass option allows users to run rules after Revit and EVOLVE have completed processing instead of before. Basically, if the Run in Second Pass option is unchecked when a rule runs and the expected elements are not colored, check the Run in Second Pass option.

NOTE: If the same parameter is being changed in both the first pass and second pass the updating of the second pass parameter(s) change will fail, throwing an error. However, parameters may be changed multiple times in the same pass.

Allow Multiple Processing

A common situation for this would be where an element is added and modified during the same execution session (e.g., drawing conduit with bends). When this value is true, the rule would execute for same element twice, once in the "add" context and again in the "modify". When false, the rule would execute only for the "add" context.

A case where you would want each:

  • False = If you have a status column and want to track when something is was just modeled (new) vs. modified after it was modeled (changed). If you draw some conduit, having this setting on false would ensure that everything drawn in the run comes in as “new” because each element would only process the element added event. If you had this setting on true instead, [most] everything would come in as “changed” because the edit event would be processed and update the status field.

  • True = When you need to always process the most up to date info. Typically this is only required when you need the geometry and it can change during a single edit session. This does incur some processing overhead as an element may actually be processed by Revit several times instead of just on the add and edit.

NOTE: that an execution session is defined as where control is returned to Revit in the since the user can select elements, change views, etc. For example drawing conduit the user cannot select elements (so the execution session remains active) until they ESC out of the drawing operation.

Relevant Articles


How did we do?


Powered by HelpDocs (opens in a new tab)