I just compiled a fresh build and rechecked this bug. It seems to me all the mentioned bugs are fixed. 1) The view correctly updates the angle values after applying the boolean operation. I am not able to get an inconsistent view anymore. 2) I'm not able to crash FreeCAD in any way I tried. 3) After...

How can this be intended? At one moment, the Angle values are 60° on the outer and 0° on the inner boolean object, resulting in a a difference between the cube of 30° and a rotation of both of 30°. The next moment the values are 60° and 1° resulting in a angle of the cubes of 59° and a rotation of 1...

For a moment I thought you were right, but as of r9586 (a bit old I know) its still not working. I made some screenshots:


Does it work differently for you?

@ickby I'm sure its not expected behaviour. At one moment, the rotation is not applied to the second boolean part and as soon as you update the rotation value, the other part jumps to the place with the value applied. The value should either be applied or not applied, but now it depends on whether y...

I recompiled with debug information and did a new backtrace: edit It seems, the old backtrace already contained all the information... whatever, then at least take the current build data OS: "Fedora release 25 (Twenty Five)" Word size of OS: 64-bit Word size of FreeCAD: 64-bit Version: 0.1...

Pure, ugly brute force. Do you think with the current design its possible to get arbitrarily rotated projections? You told me earlier that the rotation matrix was replaced with simple code, I get the feeling that the "Pure, ugly brute force" could be replaced with elegant, complicated mat...

Amazing, I'll have to look into the code to see how you achieved that! Two things I noticed: 1) The "Match 3D" button doesn't work anymore - it did work at some point, did it? 2) The section View calculates NaNs for the isometric projections. I'm not sure, how useful that is anyway but sti...

In any case, the VOM is history. It has been replaced by a Map that contains the ProjectionDirection of every secondary view based on the current front view. Lots of complex code replaced by some simple code. Whaaaaat? I mean thinking in 4x4 (wouldn't 3x3 be enough?) transformation matrices is not ...

3) techno-babble: all views are presented with +Z pointing up whenever possible (+Y when projection direction is +/- Z). I believe the is the same behaviour as the 3D view. Is this wrong in general or just for ProjectionGroups? The math to spin the secondary views doesn't leap out at me, but it's e...

So I looked at all that code again. I think TechDrawGeometry::getViewAxis needs the viewOrientationMatrix to calculate the cross variable. That function is not called in that many places. I traced the main caller back to DrawViewPart::execute, where it goes from buildGeometryObject -> projectShape t...