Closed ecdlguy closed 4 months ago
Hey, sorry for missing this issue. I agree with you, this seems like a bug. It works with a length a tiny bit over the sum, so I guess there is a greater/greaterOrEqual problem somewhere. A bandaid for now is to add a tiny amount, e.g. 1001 instead of 1000. Could also be related to floating point errors, but I would be surprised, I used integer math wherever possible.
Is https://cutsolver.modisch.me/ already using the fix?
Not yet, will try to release an update this week. Online version is v1.0.0, new one is v1.0.1
Just updated, check it out 😉 Out of curiosity: What are you using it for? I haven't found a use for zero width cuts yet
Hi,
I've done a simple test, see screenshot:![Bildschirmfoto von 2023-07-19 13-06-07](https://github.com/ModischFabrications/CutSolverFrontend/assets/8693760/20a12762-960d-45d2-9057-f57287f8da2a)
Using "cutting width = 0", shouldn't this yield 10 parts per rod?
cheers, Thorsten