SolidWorks 2011 Parts Bible - Matt Lombard [171]
Figure 12.6 shows the difference between the flyout FeatureManager on the left and the detachable PropertyManager on the right. My preference is clearly the detachable PropertyManager. When you use the PropertyManager, you don't have to go hunting for features that are listed right in front of you when you do something that opens a PropertyManager. You can put the PropertyManager on a second monitor, in the graphics area, or outside the SolidWorks window. This works best on a wide aspect monitor or multiple monitors.
FIGURE 12.6
Comparing the flyout FeatureManager with the detachable PropertyManager
You may correctly ask “What's the difference?” The difference is that when you do something like editing a sketch plane, the current state of the FeatureManager is covered and replaced by the PropertyManager. You may have had the new plane you wanted to use in view. Especially with long FeatureManagers, in both parts and assemblies, when the flyout appears, you have to again scroll to find the plane that was right in view. However you use the detachable PropertyManager, I think you will find it an improvement over the flyout.
On the downside of the detachable PropertyManager, its implementation appears to be incomplete. It does not always automatically expand when needed, and it seems to experience some graphics or display problems, such as target areas for the check and X controls not being directly over the graphics for the control.
Summarizing Part Modeling Best Practice
This section is a summary of best practice suggestions for modeling parts. Best practice lists are important because they lay the groundwork for usage of the software, which is helpful for new users and users who are trying to experiment with the limits of the software.
I believe that it is only after you respect the rules and understand why they are so important, that you know enough to break them. However, best practice lists should not be taken too seriously. They are not inflexible rules, but conservative starting places; they are concepts that you can default to, but that can be broken if you have good reason. Following is a list of suggested best practices:
• Always use unique filenames for your parts. SolidWorks assemblies and drawings may pick up incorrect references if you use parts with identical names.
• Using Custom Properties is a great way to enter text-based information into your parts. Users can view this information from outside the file by using applications such as Windows Explorer, SolidWorks Explorer, and Product Data Management (PDM) applications.
• Learn to sketch using automatic relations.
• Use fully dimensioned sketches when possible. Splines are often impractical to fully dimension.
• Limit your use of the Fixed constraint.
• When possible, make relations to sketches or stable reference geometry, such as the Origin or standard planes, instead of edges or faces. Sketches are far more stable than faces, edges, or model vertices, which change their internal ID at the slightest change and may disappear entirely with fillets, chamfers, split lines, and so on.
• Do not dimension to edges created by fillets or other cosmetic or temporary features.
• Apply names to features, sketches, and dimensions that help to make their function clear.
• When possible, use feature fillets and feature patterns rather than sketch fillets and sketch patterns.
• Combine fillets into as few fillet features as possible; this also enables you to control fillets that need to be controlled separately — such as fillets to be removed for Finite Element Analysis (FEA), drawings, and simplified configurations — or added for rendering. The trade-off is that troubleshooting is