parametric

Expected behavior

When the user selects a line and no point, pressing "m" should create a new point constrained to the midpoint of the line.

Actual behavior

Nothing happens

Additional information

This is not a bug, as "m" is meant to constrain an existing point to a line. Some users don't realize this and expect the midpoint function to create a midpoint, and that seems

https://github.com/CadQuery/cadquery/blob/ab876acc84a7df273bb368549656912a980feae3/cadquery/cq.py#L1225-L1234

Needs to be updated to use the or string selector, fluent api, and remove the saveModel call.

See @sdrave's comment here.

The banner I threw together is terrible.

If you got any design chops please update this.

to allow broadcast features like:

setSolverParams!(fg, :graphinit, false)
setSolverParams!.(fg, [:drawtree, :showtree, :dbg, :treeinit], true)

this would be a partner to existing getSolverParams

When using the PortCutterRotated component, polar_coverage_angle attribute cannot be greater than 180 and a Standard_ConstructionError is raised.

This might be due to lines below:
https://github.com/ukaea/paramak/blob/7f5acbd65f904a1ccb527e061a3b7e3f86b8a26f/paramak/parametric_components/port_cutters.py#L151-L163

How to reproduce

from paramak import PortCutterRotated

We could do with 3d models for some of the missing components.

I don't think we should do every component but could do with updating the /docs/source/paramak.parametric_components.rst file for the following components:

• VacuumVesselInnerLeg
• CuttingWedge
• HexagonPin [example h