API vs UI projection

[teanau]

I want to project a body to gets its shilouette then project all faces with a specific normal.  

But it seems the api will only accept edges one at a time?

vs interacively i can select a body or a face to project?

This results in annoyingly fragmented dxf files that dont keep edge loops intact much like solidworks exports dxf files.

what black magic is going on under the hood of the interactive projection meathod? and how can i replicate them through the api?

thank you

_sam

[ekinsb]

Can you please provide more detail about the workflow that you're using in the user-interface?

[teanau]

wow, that was an alarminglty quick reply, thanks

create a body  ( a panel of plywood with a few holes and pockets  cut in it )

create a sketch on a planar face

run the sketch > project command 

     select the bodies option and select the panel body ( results in a shilouette of the body projected )

run the sketch > project command 

      select a pocket face with a normal matching the sketch referecen face ( this projects all the faces edges connected as an edgeloop )

I may be doing something wrong, but i dont appear to be able to feed the API project anything but single edges

thanks for the support

_sam

[ekinsb]

The project method on the sketch should support taking a BRepBody object as input, but it currently does not.  I'll file a bug on that.  I don't remember if that capability was added to the product since we did that part of the API or if we just missed that in the initial implementation.

The project method does accept a BRepFace object as input but in my testing now I see that the result is not correct.  Instead of getting sketch entities for all of the edges of the face it's just getting one edge.  I'll file a bug for that too.  Thanks for reporting these.

[teanau]

Thanks for looking into these, this will be huge for me.

The behaviour you explain with faces is the same as what i experienced, i guess its the first edge of each face only.

all the best

_sam

[MattWynn]

yeah Brian, this is the same kind of thing we will be needing to do

[teanau]

curious, did this make it into tomorrows update?

[ekinsb]

Unfortunately we were too late to get it into tomorrow's update.  But the problem has been fixed and will be available in the next update, which is currently scheduled for the end of May.

[teanau]

can i give you more than one kudos?

 thats great news and i really appreciate the info