Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

UP_TO_NEXT with scope?

Evan_ReeseEvan_Reese Member Posts: 1,368 PRO
Is there a way to limit the scope of an UP_TO_NEXT endBound in a custom feature? Otherwise it can sometimes behave unintuitively. For example, if the feature is creating multiple extruded bodies using a loop, and the second body runs into the first one.
Evan Reese / Principal and Industrial Designer with Ovyl
Website: ovyl.io

Answers

  • MBartlett21MBartlett21 Member, OS Professional, Developers Posts: 2,000 EDU
    I don't think there is any 'official' way to do it. You should be able to approximate it with another way, though, like creating a new context, deriving everything you need, extruding in that context, then deriving the extrude back.
    mb - draughtsman - also FS author: View FeatureScripts
  • Evan_ReeseEvan_Reese Member Posts: 1,368 PRO
    Thanks! I haven't messed with multiple contexts at all yet, but this sounds like it would do it. Would this incur the same performance costs that the native derive feature does?
    Evan Reese / Principal and Industrial Designer with Ovyl
    Website: ovyl.io
  • MBartlett21MBartlett21 Member, OS Professional, Developers Posts: 2,000 EDU
    I expect it would (twice!) 
    mb - draughtsman - also FS author: View FeatureScripts
Sign In or Register to comment.