that define the entities.įor the specific application here, I might suggest that you set a bitmap image of the airfoil as your background (under "line styles" from the home screen), and then trace it with a spline. The request generates the entities, and the parameters set the initial position (before constraints are solved, if applicable) of the points etc. When a sketch is opened directly, only the requests and parameters matter. That's what Entity.actPoint is for it has no effect when a sketch is opened directly. slvs file only for the benefit of assemblies, which load those cached entities to avoid the need to regenerate each imported part. DOC.txt for the library is probably your best reference there, since the entities and parameters exposed in that interface correspond very closely to the internal structures.Įntities are exported in the. There's no explicit documentation for the. It would help if someone posts an example blurb of an slvs file that adds a point with some guidance as to how to connect the various Entities to create a line segment or polyline.Īs always, a big thanks for this excellent piece of software.Ĭhinmay's post is basically correct. Otherwise, automatically generating an SLVS input file from airfoil data should be possible. So, it's not just Entity.actPoint, but a few other places to make it consistent. In doing so, I wasn't quite sure how the Entity.h.v, Entity.type, and other properties associated with a point should be handled.Īlso, the location of the points need to be added as Params, it seems. You can modify the text file to add a bunch of curves with the intended points. Instead of having Solvespace import curves, one could modify the solvespace input. Someone had suggested a work-around earlier and it might work for you.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |