Unexpected behavior with joints not following sketch points.

[steve3957T]

When inserting a part into a design, it always drops at the origin point.  Typically, I have something already there, so I move the part a bit so I can see it better.  Then I use joint to place the part where it belongs.  Problem is, if I do it this way, the joint doesn't stay in the right spot if anything moves.  If I don't do that move after inserting, it works as expected.  Is this a bug or is there a better way to do what I'm trying to do?  If I don't move a little after inserting, it's difficult to select the right spot for the joint if there is something else at the origin point. 

I'm attempting to attach a screengrab of what I'm talking about.

[jeff_strater]

interesting.  I cannot tell, from the video, what point you actually picked on the sketch.  From the video, I wonder if it was a midpoint instead of the sketch point.  I tried a simple case, and it seems like it works OK:

[steve3957T]

Not a midpoint, the sketch is just 2 rectangles.  The long line in the back is actually two that connect at that point.   Your video starts after the part was inserted.  Did you move the part after inserting?  This is what triggers the behavior on my end.

[steve3957T]

Just to add to the weird behavior, take a look at this video.  I make one joint that does not work as expected, undo and make the same joint that works correctly.  The only difference is on the second joint, the second selection, I move around until the profile in the sketch is not highlighted before making the second selection. 

[jeff_strater]

Nope, Insert or Move does not seem to matter.  See below.  Can you share that design here?  Either share the design after the insert, or share both the inserted component + the component with the sketch.  Thanks

[jeff_strater · Accepted solution]

aha!  That was it.  Yes, I think there is a bug there.  You can snap a joint to a profile corner (or center), and it shows that behavior, that, I agree, is wrong.  Nice debugging.

[edit] I created bug FUS-140590 for this.  Thanks again for your persistence in chasing this down