Performance Tips for Ideate StyleManager
Ideate StyleManager can be used to analyze, merge, rename, and delete different kinds of styles within a Revit project, template or family file. In this topic we will review performance tips per these processes. These tips apply to the use of Ideate StyleManager within the project environment. Performance within a template file or within a family file does not typically present a performance challenge.
The analyze process will be relatively quick when applied to filters and scope boxes and is not needed for material appearance assets or for view templates. The analyze process presents the biggest performance challenge when used on object styles, line styles, line patterns, and fill patterns.
- Don’t try to analyze all styles at once or start and go for a coffee.
- Analyze may touch many elements of the project. To optimize the performance of analyzing within a workshared project we recommend that the work should be done when no one is in the project.
- Any style that is likely to be used by many elements (instances) or families will likely take long to analyze. An example of this would be object styles for curtain panels or for pipe fittings.
- Several styles are set as the default in much of the out-of-the-box content and will therefore result in a particularly slow analyze process. Some of these common Autodesk styles are:
- Line pattern: Dash, Dash dot
- Fill pattern: crosshatch diagonal
The merge process performance will vary greatly depending upon the number of elements listed for usage and the worksharing status of the elements that need to be modified.
- Merge may touch many elements of the project. To optimize the performance of merging within a workshared project we recommend that the work should be done when no one is in the project.
- Use Delete instead of Merge if the style is not needed.
- Always use Delete for any fill pattern called *. These are internal fill patterns often seen when English and non-English content has been merged.
The rename process is simple and does not result in any performance issues.
The delete process will be relatively quick when used on these styles: material appearance assets, filters, view templates, and scope boxes. It will also be quick when used to batch-delete any style that is unused. If a style is in use then the performance of the delete process depends on the number of items that need to be modified. When families are listed for a usage (as opposed to an element, type, or view template, for example) then Ideate StyleManager will be opening a local copy of that family in the background.