DInsight

Hello Leo
We have implemented per face color in v7.0. It should be out later this year. It is persistable via .mdg. Step persistence needs a bit more work which we have left for little later. Get in touch if it is urgent.
Thank you for your interest

This has been answered here:
select a point in a cloud

Regards

Hi Tyler It is a good question. If you know which edge is shared you need to find parameter of the nearest point on the edge. It can be done either in 2d or 3d. This is the 2D way: if uv is the 2d point you have, IBRepFace_DG face; IBRepEdge_DG edge; int side = edge.FindFace(face); double outMinPara...

Sub-shapes of BRep geometries do not have a name unfortunately. They are considered a pure geometric attribute. You could probably setup a map in your language to assign any per shape name or data.
IBRepShape_DG.GetHash() is a good candidate of a key for the map.

Regards

Hello Projecting vector to a surface normally means projecting it to the tangential plane at some surface point. The solution depends on whether you have a fixed point on the surface or not. The code below assumes that you have also a location point for the vector (So you have a ray) and you need to...

Hi Jon
This topic should work for general curves as well. May be with a slight modification.
It has to be done per face in this version

Regards

Hello Josh Not directly. DGKC is two levels of abstraction above a graphics library. For the long term it would be better to recode your app using entities. If you need something quick you could use IDraw_DG interface. It "draws into an entity", which can be persisted, rendered, etc. There is also a...

Starting from update 5206 the second part can be also done as:

Hi Joey It looks like the easiest way is to use 3D wires with all z coordinates set to zero to model a single curved arcs/lines polygon. Have a look at BuildWire() in the main form Shape Builder sample. Instead of bspline curves you can use circles or lines for the edge curves. See ShellBuilder.Upda...

Hi Jeff Sorry about the bug. We know about it but it somehow got through the cracks in priorities. It happens inconsistently in our tests. I have raised its priority. In my experience I always could get around it by restarting Visual Studio, rebuilding the project, etc. Remember that for x64 product...