Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- 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.
Best Of
Re: chamfer / fillet for inside undercut corner.?
I think the corner overcut FS might be able to do the job?
https://cad.onshape.com/documents/b99915c0b73924ca981bc57f/v/615cb6d9633a595a6bc99f8a/e/14458d1263a98640a0cf663c
Re: What is the `op` intended to convey in certain featurescript library?
Yep. The idea is to have a set of orthogonal primitives. E.g., extrude performs an opExtrude, possibly with an opBoolean and an opDraft.
_anton
Re: Get corresponding queries in patterned things?
Well the thing that got me curious about it was a sliding door kind of a thing that traced an unintuitive path. I think should have worked with it, but I was struggling to do it, so I ended up patterning it manually. With the help of 3D points and Query Variable, I was still able to get a parametric query for the points to do a fit spline through.
Oh btw, now that approximateSpline is here I'm opting for that over fit spline, so that's another reason to explore. But mostly, I'm just following my curiosity and seeing where it goes.
Re: What is the `op` intended to convey in certain featurescript library?
I believe op is short for "operation" (ev is short for evaluate)
extrude is the user facing feature. This is literally the standard feature that shows up in the tool bar.
A feature is just a function, so features can call other features. There is nothing stopping you from calling the standard extrude from your feature - and in some corner cases (like sheet metal) its the better option.
opExtrude is the base level call to modify the context, its as low as your featurescript gets before things get sent to the black box that is the back end of Onshape. While opExtrude is missing some functionality of extrude - that missing code also means its going to be a bit more efficient. Standard features have a lot of quality of life meant for users that your FeatureScript might not need. A simple feature might not be noticeable, but when you get to more complex features, the regen time of your code can quickly add up.
There exist op functions that don't have a full feature counterpart, and some full features don't have a base level operation.
