Redundance constraints as an opportunity to fix the sketch FLIP.

[kaiwas]

Is there an existing issue for this?

• I have searched the existing issues

Problem description

Topic for discussion about fixing a pretty serious problem.
As everyone knows, there is a problem with turning over completed sketches. Despite the fact that they are completely constrained and have a beautiful green color, such sketches can have several possible solutions from the solver's point of view.
Is it correct? The user sees green and assumes that he has done his job (will have a predictable result). But that's not true! Maybe the sketch shouldn't be green if it can have multiple solutions?

I know that to solve such a problem I have to completely break the work already done and reassemble the sketch in the “correct way” (but I don’t always know the right ways).
Instead, I could assign an additional constraint to solve the problem in one second.
But I can’t do this because the excess constraint turns the sketch red and is removed.

In my opinion there should be an additional opportunity to indicate to the solver the necessary solutions.The current behavior limits not the solver. The current behavior limits the user. The user should be in charge, not the solver. If to solve a problem the user needs to drive a nail into the monitor, this should probably be the case.
"You" can call the fixing constraints whatever "you" like. They may not be current. But one solver solution is always better than 10. And if for this you need to assign another constraint, there should be such an opportunity. This is useful.

The test file is attached.

Flip_sketch.zip

(UPD/

I thought again. Probably my proposal would not always solve the problem.
But at the same time, I understand that additional (duplicate) constraints could be useful in some cases. But if this cannot be done programmatically, or if something breaks because of this, then of course you need to leave everything as is.

In short, we need some kind of ability to “fix” a sketch without recreating it. Variations:

1. Use redundant constraints
2. Use some kind of constraint priority. SO that the less important ones are deleted. (the user himself would decide which constraint is more important and mark it).

If you think that the current situation does not require improvement, just CLOSE THE ISSUE
)

Full version info

0.21.1 & any versions

Subproject(s) affected?

Sketcher

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct