Cannot move spline points that are not constrained

[Anonymous]

Points on this (selected) line are not constrained, however refuse to be moved by click dragging. Is this a bug or what could be going wrong here? Thank you. 

[davebYYPCU]

Which point does not move?

Of the four points on that spline 3 appear to have been constrained, only the top left internal point would be free to move, based on your pic.

the overlapping construction lines (mirror position) is not ideal.

Might help....

[Anonymous]

That free point is not movable, but none of the handles on any of the splines are movable, either. Please reference the attached fusion file. thank you. 

[davebYYPCU]

Well that's weird, Click Drag, and Move Tool did not want to cooperate, then I found you can't click drag anything in this sketch,  totally locked up. 

How does one circle become fully constrained without reference to the Origin?  Was there anything in Sketch 1 that is no longer with us?

Edit: Ok, Adding this dimension with default length made no difference, but changing it to 21 unlocked the sketch and I could click drag spline points and handles in the sketch, but the 21 dimension distorts the sketch - undo locks it up again - so no better off.

One for @jeff_strater to fathom out.

[Anonymous]

Thank you for the help so far. I personally feel like I am running into this behavior when dealing with splines on a semi-regular basis. 

[jeff_strater]

It turns out that there is one problem spline here - the bottom one in this orientation:

if you delete this spline, things seem to get freed up.  I've sent this off to the sketch team to take a look at.  You could try to re-create this spline.  My attempts seem to be OK, but I'm not sure I re-created the exact same curve.

[jeff_strater]

Had the sketch team investigate.  It turns out that there is a degenerate tangent handle at the end of the problematic spline that is the root of the problem.  If you deactivate that tangent handle, the sketch is OK again.  You can re-activate it, and adjust it as needed, but that is the root problem.  We will look at putting checks in to prevent this situation from occurring in the future, so thanks for sharing this design, @Anonymous , as it revealed a previously-unrecognized problem.