Improvements to Onshape - May 26th, 2016

ilya_baran

@clayton_ertley
A word of caution about the MultiSplit feature above though -- referencing topology created by this feature (for example filleting an edge along the split) will not handle changes to the "Entities to split with" correctly in all cases: for instance, if you:

MultiSplit Part 1 with Surface 1 and Surface 2
Fillet one of the edges split by Surface 2
Delete Surface 1 from the "Entities to split with" in the MultiSplit

Then the fillet will fail even though its target edge still exists.  In making other changes to the MultiSplit, the fillet may apply to the wrong edge.  In the future we'll make it easy to avoid these robustness issues (in this case, they are caused by using the index of the query results as the opSplit operation id).

clayton_ertley

ilya_baran

Tanks for the heads up.

 

fastwayjim

FeatureScript is a game changer!

michał_1

FeatureScripts shows how whole idea of Onshape is thought through. No dev kit? Just another tab? I'm amazed.
Other vendors might have some advantage over Onshape, but it's just a matter of time. Future belongs to Onshape.