8 Replies Latest reply on Jan 3, 2017 2:03 PM by Rick Becker

    Avoiding disrupting the Feature Manager Tree....

    Daniel Cane

      Hi,

      Sometimes when I drag surfacing features up the feature tree, I get this message:

      xx.JPG

      Prior to letting go of the mouse click to drag it, I have the blue arrow

       

      DSC_0002.JPG

      Which I’ve always taken to mean ‘OK to move’

      Not the black hazard sign which I’ve taken to mean ‘NOT ok to move’

      DSC_0003.JPG

       

      The two options in the dialogue don't offer me what I want, which is to be able to decide to not move the feature after all if it's going to cause trouble. What you might use 'Cancel' or Ctrl+Z for in other circumstances.

      The consequence moving it to the wrong place this can often be this awful cascade of broken and disrupted relations that messes-up the model.

       

      So my question is please: is there a way to not move them higher than is safe to do so, OR a way to undo the damage it causes and prevent the chain-reaction of messed-up relations.

       

      Many thanks!!!

       

      D

        • Re: Avoiding disrupting the Feature Manager Tree....
          Rick Becker

          I try to Save before doing anything that has historically caused disruption to the tree or other things.

           

          If my Tree turns into a Christmas Tree (lots of pretty shades of Red and Yellow) I close the file, not saving, exit Solidworks and try something else after restarting/reloading.

            • Re: Avoiding disrupting the Feature Manager Tree....
              Daniel Cane

              Hi,

              Yeah this is what I've been doing so far as well...

              It feels like an imperfect solution. :-)

               

              D

              • Re: Avoiding disrupting the Feature Manager Tree....
                Dwight Livingston

                Rick Becker wrote:

                 

                I try to Save before doing anything that has historically caused disruption to the tree or other things.

                 

                If my Tree turns into a Christmas Tree (lots of pretty shades of Red and Yellow) I close the file, not saving, exit Solidworks and try something else after restarting/reloading.

                Rick

                 

                I would not necessarily back off because a whole tree goes red. The trouble might be a single small conflict. Repair the highest red item and that may fix the whole thing.

                 

                Dwight

                  • Re: Avoiding disrupting the Feature Manager Tree....
                    Rick Becker

                    I love the optimism Dwight Livingston.

                    Been there done that as the saying goes.

                     

                    I have tried it every which way I can. I have indeed found that sometimes a fixing a single red item works, and sometimes it doesn't.

                    But the more times I correct the Christmas Tree reminds me of the poisonous M&Ms analogy.

                     

                    Imagine a bowl of M&Ms. 10% of them are poisoned. Go ahead, eat a handful of them. After all, they are not all poisonous!

                     

                    Being burned teaches one not to play with fire and to take the safest rout in the future.

                     

                    Just a couple of months ago I was in the midst of a revision on a large progressive die design. It was late and I was hungry, so I saved and went home for the night. Everything saved correctly with no error messages.

                    Come back the very next morning and open the assembly. I had to double check the calendar to make sure it wasn't December because I saw the prettiest of Christmas tree.

                    I carefully rethought my last steps and did my very best to deduce what the culprit could possible be, hoping beyond hope that, this time, it was the highest red item.

                    Alas! To my great dismay I started down a full two day journey of angst and trepidation is pursuit of the elusive Healed Tree.

                     

                    I believe that I am not alone.

                    Thank you for your thoughts Dwight.

                • Re: Avoiding disrupting the Feature Manager Tree....
                  Jim Wilkinson

                  Hi Daniel,

                   

                  This is a very generic dialog that comes up whenever the FeatureManager tree is rebuilding and encounters a new error. A new error in the tree can be triggered by a large number of different operations. So trying try implement a cancel button on the dialog that would undo the last thing that you did generically would be very difficult to do. Users also don't want us to make the reordering so strict that it will prevent all possible downstream errors; it used to be a lot more strict and you'd simply get the black (re-order) in more cases, but it made modeling very inflexible.

                   

                  If you choose "Continue (Ignore Error)" can you not then hit undo (Ctrl-Z) to get back to the state before you did the re-order?

                   

                  Thanks,
                  Jim

                  • Re: Avoiding disrupting the Feature Manager Tree....
                    Craig Schultz

                    In the second pic it looks like you are going to place it after "Inside 3B" which is one of the parent features.  You can tell the parent(s) by the blue spline arrows.

                     

                    The third pic looks like you are placing it above "Inside 3B", which shows you the back do not enter symbol.  And if you do move it above the parent, you will get those feature "trees of blood".

                     

                    There is no way to avoid moving it.  The best you can do is hit the "Stop and Repair" option.  Then hit CTRL+Z

                    • Re: Avoiding disrupting the Feature Manager Tree....
                      Daniel Cane

                      Testing both here now, it appears best to:

                      "Continue Ignore Error" > "Close" the "What's Wrong?" dialogue > CTRL+Z

                      Choosing "Stop and Repair" leaves it rolled back, meaning I have to roll it forward bit-by-bit and repair all the messed-up relations stepwise.

                      Thanks for your help guys!!

                      Daniel