This adds the ability to enter things like 6 * 25.4 into the distance line edit widget during scaling operations in the image workbench. Can also enter something like math.pi * 3 or 2**3, etc. Basically, any legal python input can be used.
Using eval() is not considered a secure way of doing things, but in this context the user would be entering malicious code into his own computer. Also, what can the user do in eval() that he can't already do just by entering directly into the python console?
urllib2 in Py3 gives us a bytearray instead of a string. We have to decode it first to get the metadata.txt. When decoding fails we assume that we are in Py2 and process as before.
===============================================
It is a long felt need that redundant constraints are not generated while autoconstraining.
The solver sketcher in v0.17 is überpicky with redundants due to the new popularity contest algorithm. The former behaviour is exhacerbated.
This new mode enables automatic redundant constraint removal.
In UI operations IN EDIT MODE, upon detection of redundancy by the solver, the Sketcher will remove all redundant constraints detected by that solve.
This makes the sketcher much less annoying.
How to test this?
The easiest example is to create a vertical line. Then make the endpoints symmetric with respect to the horizontal axis. Without this mode,
the vertical constraint and the symmetry constraint are redundant. With this mode, the vertical constraint gets automatically removed by the Sketcher.
==============
- Zero initialization of the jacobian matrix
- Correct notification of redundant/conflicting in presence of non-driving constraints.
fixes#3529
The property "FluxVariable" of the FluxEquation document type was
exported wrongly by sifio. This was because sifio didn't recognise
unicode as a string and exported is as an array of chars.
