The development of a new “Project Designer” tool is recommended, modeled after the existing Library Designer. This feature would allow users to make targeted modifications to products and subassemblies within a specific project, without impacting the global library or requiring complete project regeneration.

The new feature would utilize the same interface and structure as the current Library Designer, ensuring a familiar and intuitive experience.

A separate database file, MicrovellumProjectDesigner.sdf, would be created and stored within the individual project folder.

This database would mirror the internal schema of LibraryDesigner.sdf, but would be scoped exclusively to the scanned products and subassemblies of the selected project.

Any modifications made in the Project Designer would be committed only to that project's product data.

Granular Project Control: Users often need to make project-specific changes without altering the master library. This feature supports that workflow, allowing for quick and safe edits.

Non-Destructive to Library: Maintains the integrity of the global library while enabling powerful customization at the project level.

Revives Legacy Functionality:

Previous library versions allowed users to update projects via shared subassemblies like carcasses. The newer Foundation Library lacks this flexibility, as it no longer uses a subassembly-based approach. This feature reintroduces that capability in a more robust and project-contained manner.

Enables users to correct or enhance all products in a project without rebuilding from scratch—saving substantial time and minimizing disruption.

The “Project Designer” would fill a critical gap in project-level customization, offering both flexibility and control for users working with complex or evolving design requirements. It leverages proven UI and database structures, minimizing development overhead while delivering high user value.