The following article highlights a new feature that allows users to update their project-level hardware machine tokens from the template.
Currently Microvellum Software does not support automatic library synchronization for newly added hardware machine tokens at the project level. This omission was intentional due to the fact that machine tokens can and in most cases do contain dependencies from other workbooks (Wizards, Globals, Hardware, etc.). We recognize that this was problematic for some users and caused a little frustration from time to time. The vision of this feature is to allow for a manual (user triggered) approach of updating a project’s hardware machine token from the selected template’s specification group. You can use this feature for a couple of things:
Add machine tokens to the project’s hardware file from newly added template hardware items.
Replace existing project hardware machine tokens from a selected template file.
All selected project hardware item’s machine tokens will be replaced with those of the matching template hardware item. Once complete, the operation cannot be reversed. All machine token dependencies must be added to the project by the user manually (Wizard, Global, Hardware Names, etc.). Missing dependencies will render the machine token(s) unusable.