Diagnose part Health: Sick sketch points

Diagnose part Health: Sick sketch points

robmatthews
Collaborator Collaborator
709 Views
2 Replies
Message 1 of 3

Diagnose part Health: Sick sketch points

robmatthews
Collaborator
Collaborator

Within a part, I'm trying to identify sketch points that are generated from projected geometry, but the geometry is subsequently changed higher up the feature tree, leaving a pink sketch point (or worse).  What attributes would such a sketch point have?

 

 

=============================================
This is my signature, not part of my post.
0 Likes
710 Views
2 Replies
Replies (2)
Message 2 of 3

ekinsb
Alumni
Alumni

You can try this, which I believe will work.  First check the Reference property of the sketch point.  If this returns True then the point was created by projecting geometry.  Next check the ReferencedEntity property.  If this returns something then then connection to the original entity that was projected is still ok.  If it returns Nothing then the connection has been broken.


Brian Ekins
Inventor and Fusion 360 API Expert
Mod the Machine blog
0 Likes
Message 3 of 3

robmatthews
Collaborator
Collaborator

Thank you for your reply.

I tried that too, but no, as it happens, that method does not work for the example I am using (attached). It returns [Sketchpoint].ReferencedEntity.count<1 even when the line (or arc) is not pink. I think it returns 0 when the line was projected from another part from within an assembly, and then the adaptivity turned off again. 

 

The attached zip has all the code I've got so far, as well as the test part. (This particular part was initially much more complex, but i had removed all the later geometry to simplify for the pupose of checking.)

 

If you put a break point on line 291, it'll take you straight to the sketch with the dodgy points, and I'm just putting a circle in on any point in question to identify it. There should only be one circle created in the sketch; instead there are four.

 

I look forward to hearing from you again, Brian.

=============================================
This is my signature, not part of my post.
0 Likes