Home› Using Onshape› FeatureScript

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.

Limit UP_TO_NEXT to the merge scope?

EvanReeseEvanReese Member, Mentor Posts: 2,135 ✭✭✭✭✭
in FeatureScript
Is it possible to use opExtrude with an UP_TO_NEXT end condition that doesn't reference everything in the context? I'd like to limit it to my merge scope (or a queried set of bodies I choose).
Evan Reese

Best Answer

Answers

  • EvanReeseEvanReese Member, Mentor Posts: 2,135 ✭✭✭✭✭
    Sure will. thanks!
    Evan Reese
  • EvanReeseEvanReese Member, Mentor Posts: 2,135 ✭✭✭✭✭
    ooh, I may have spoken too soon. If the body query has more than one body, it seems to only take the first one I selected. that means one of the extrudes will always miss the bounding entity. see the hexagon and circle extrudes below.

    Any idea how to get that working? I'd love to avoid adding another query field.
    Evan Reese
  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,686
    I'm not sure what the image above is supposed to look like, but I tried a few things with faces and could not get it to work. The only way I can think of doing this is to make a copy of the bodies then boolean them together but that could be very expensive.
    Senior Director, Technical Services, EMEAI
  • EvanReeseEvanReese Member, Mentor Posts: 2,135 ✭✭✭✭✭
    Hi Neil, I made a 1-minute video showing what I'm going for and what I'm stuck on here. Are videos like this preferable to me trying to write it out?

    I considered copying/booleaning bodies, but, aside from being expensive, if the user has already added part clearances, they wouldn't boolean anyway. I guess I could just add the full set of end conditions like the standard extrude, but I'm trying to make the feature UI minimal (and so far, you can see I'm failing at that :D , but it's a work-in-progress).
    Evan Reese
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Sign In

Categories

Vanilla Forums