cad

This may be a good issue for someone wanting to eventually get deep into the geometry code of Solvespace.

issue:

Triangulating a NURBS surface is currently O(n^2) operation, and in many cases it doesn't produce very good triangles. We should be able to have better quality in O(n*log(n)) time.

background

For surfaces with compound curvature (a torus for example) we use "grid triangul

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.

Here's what a CI workflow currently looks like, when viewed in the GitHub UI:

It's hard to see what's going on with all those Cargo actions, on first glance. It would be much better, if those jobs had names, like cargo build, cargo test, etc.

The configuration for the CI build

Tuo Xie requested the ability to visualize clocking (pins & wires I believe). We should make it easier to visualize subsets of the device routing resource and types of routing nets.

Proposed Behaviour

Add filtering to the rr_nodes displayed (ToggleRR), and to the nets displayed (ToggleNets). I think we should have an option to filter what is shown by node type, node name (segment or pin t

dwgadd is unusable:

• Need of "\n" at begin of first string, sic.
• issue with initial = 1 at begin and setting to intial after initialization
• No error message to stderr in each exit(1)
• Missing error in stderr in dwg_add_dat (&dwgp, &dat) != 0