Adrián Insaurralde Avalos
Adrián Insaurralde Avalos
what are you fixing? You are breaking the formatting of these strings, see https://peps.python.org/pep-0498/ There's a few where using f-strings is unnecessary but most of these are evaluating variables so...
There is already an issue for the underlying problem: #5673, at most the info that it prevents auto constraints from working should be added there.
IMO yes, but @abdullahtahiriyo would be the right person to ask. And maybe also @realthunder since he has this solved in his branch, but he's probably busy with TN stuff.
fixed by #7417 this can be closed
That's a problem in the CI itself because it's not actually running a full compilation, it just runs some checks (see #7152) actual compilation CI is the one running on...
do you want a snap build of this? @luzpaz should be able to create one if necessary
I built and tested, the reverse checkbox appears to have no effect when two angles are selected (and possibly other modes). Also having the first angle default to 360 makes...
No such issue that I noticed but note that I did really minimal testing, perhaps something like 90 or 180 could be a good default for two angles, the problem...
> It is, I suppose, depending on how we define "mode". If "midplane" cases are considered different modes it's not valid there. Symmetric does make reverse irrelevant but with modes...
breaking down the preference is a good idea but "Appearance" is not a good title to have units and startup settings IMO. Additionally to the stuff proposed here IMO it...