Properly organizing and naming the different views in your project browser can save you from losing important work. This article provides a simple, yet often overlooked, step in the detailing process: renaming your views.
Key Insights
- Renaming views in the project browser is a crucial step in the detailing process that is often overlooked.
- By giving each view a specific name, you can prevent accidental deletion during a cleanup of the views in the model.
- Developing a habit of properly naming each view will help in maintaining order in your project browser and prevent losing views that are actually necessary.
Before we move on to detailing, we need to do one very important thing, and this oftentimes gets overlooked because it's such a simple step that people always forget to do it, and that is just simply renaming our views. So I'm going to go into my Project Browser, and I'm going to look for Sections and Wall Sections. So I'm going to go ahead and I'm going to rename this instead of Section 1 Callout, which is the view we're currently in here.
I'm going to go ahead and rename it Wall Section 1. By renaming it, it's no longer a generic name, so if somebody comes around and decides they're going to clean up all the views in the model, and they see something like Section 1 Callout 1, it's probably going to get deleted because they may or may not look at it, and you'd hate to lose all this work, right? We want to make sure we're renaming these things. So Section 1 here, I'm going to rename this one to Building Section 1. Section 2, I'll rename it to Building Section 2. This is a good habit to get into because the last thing you want to do is have many nondescript names in your Project Browser, and you have no idea which views are actually being used, and it could be easy to lose a view that you actually need because somebody could go through and easily delete it. So just take the time and make the effort to rename those as you see fit.