Should .location_at(t) use FrameMethod.CORRECTED by default?

[snoyer]

.location_at(t) and therefore curve ^ t currently use FrameMethod.FRENET by default but FrameMethod.CORRECTED can give nicer results, see following example:

• top: curve ^ t
• bottom: curve.location_at(t, frame_method=FrameMethod.CORRECTED)

from build123d import FrameMethod, Spline
from numpy import linspace

from ocp_vscode import show_all


path = Spline(
    (-40, 0.0, 0.0),
    (-10, 5.0, 15.0),
    tangents=[(1, 0, 0), (1, 0, 0)],
)

frames = [path ^ t for t in linspace(0, 1, 20)]

path = path.translate((0, 0, -10))
frames_corrected = [
    path.location_at(t, frame_method=FrameMethod.CORRECTED) for t in linspace(0, 1, 20)
]

show_all()

This should just be a matter of changing the default value, however there seems to be an OCCT bug where a loop will not terminate for some curves (upstream issue: Open-Cascade-SAS/OCCT#370). For example:

from build123d import FrameMethod, Spline
from numpy import linspace

path = Polyline((-10, -70, 0), (0, -70, 0), (0, -70, -20), (0, -60, -20))

frames = [path ^ t for t in linspace(0, 1, 20)] # ok

frames_corrected = [
    path.location_at(t, frame_method=FrameMethod.CORRECTED) for t in linspace(0, 1, 20)
] # hangs