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.
Options
Place where I can find some more descriptive documentation on EntityInferenceType
Hi there,
Just want to check where can I find some descriptions for EntityInferenceType enums? It seems the documentation column for this type is empty in the feature script doc.
Thanks!
Just want to check where can I find some descriptions for EntityInferenceType enums? It seems the documentation column for this type is empty in the feature script doc.
Thanks!
0
Comments
I will put in a ticket internally to document this enum. Thanks for pointing it out.
Once the descriptions are generated I will post them here as well so you don't have to wait for the push.
Still working on this, but I realized that this Enum is only used in the `mateConnector` feature. When using FeatureScript, it would be better to make a call directly to `opMateConnector` (the underlying operation which adds mate connectors to the Part Studio) rather than the `mateConnector` feature, which is the code that is called when the user clicks on the "Mate connector" button in the UI. (i.e. it is a Feature, in the same sense that your custom feature is a Feature)
https://cad.onshape.com/FsDoc/library.html#opMateConnector-Context-Id-map
This is a good general rule when programming in FeatureScript. It is easier and faster to call `opExtrude` than `extrude`, `opRevolve` than `revolve`, `opSweep` than `sweep`, etc.
Finished this up, it will be available in an upcoming release. In the meantime, here is the documentation for those fields (the undocumented ones are not implemented for FeatureScript, and will always fail)