@johnsonshiue wrote:
The point of grounding components is to ensure they stay put regardless what constraints are changed or what components are moved.
Many thanks!
@johnsonshiue Agreed! I'm big on design intent, if the intent is that a component should not adjust, then constrain it as such, or ground it. The option of placing and grounding the first component in an assembly is one I always have checked. This is just an example where grounding is good practice. But yes, if the design intent is for a component not to move during edits, set it as such.
But I'm referring to users doing a blanket grounding. Grounding EVERY component as well as having them constrained. There simply isn't a reason for this practice. When edits do happen, the user is forced to unground everything, adjust/constrain, then reground everything again.....why?
I had one user claim they did it so items wouldn't "shift" by accident. If are constrained properly, they won't.
Honestly, I think it's due to a lot of users don't understand nor like the constraint process, especially when it comes to editing and they get a ton of errors during the process. I personally know a few users that when opening a file and they saw all the constraint errors, they were overwhelmed. Once I explained and showed them that correcting one blown constraint error can actually clear a slew of others, they were a bit relieved. But I still think users panic or get frustrated and since they can easily ignore these until it gets to be too much, they simply kick the can down the road, hoping the next guy will fix it.
This is where the Angry Elf gets angry, fix your "bleeping" files!
