Martin Siggel

Ah okay... I thought, the epected point could be derived from the ellipse equation, but this list is probably also okay.

> Passing -DPython3_EXECUTABLE=/usr/bin/python3.8 to cmake looks like it might work to select one version. This is correct. The project cannot be built for multiple versions at the same time. This...

This is a known issue and seems to be a Qt (4?) issue on Linux only. We cannot fix this unless we are completely implementing our own way? Maybe it...

@ErwinMoerland The current function to compute the intersection of a plane with the aircraft model is to simply give tigl the plane equation (e.g. point on plane and normal vector)....

I can reproduce the bug. Somehow, these profiles trigger the linear solver to fail. This probably means, that the linear system in ``CTiglBSplineApproxInterp:: solve`` is ill-posed and the matrix is...

In theory, kinks and guidecurves should be compatible. I have to look into it, what causes the bug. If you look closely, there still is the kink at param =...

Here's my analysis about the issue. Actually, I see here two problems. One is a true bug, the other one is an inconvenience. 1) Bug: The guide curve is placed...

I think the function would be more versatile, if the user can provide a uID. This uID could be either a geometrical component or even the whole aircraft (which then...

Okay. According to @ErwinMoerland , the function is okay from the API as it is. There is though the test case `` GetCrossSectionAreaSimple.sanity_values`` which still fails.

I don't think that this is easily possible. A kink creates a non-continous derivative in the whole loft surface, even though, it is defined on only some sections. The reason...