Max Gaukler

Do we really want this? I fear this could cause two limitations in the long term: - restricts laserScript to the rather simple features that LibLaserCut offers (no interactivity, no...

Should be better now. I added tests, but am not sure how `workprec()` is supposed to work for `iv`. Is that a bug or by design?

You can now cheerfully update the https://github.com/t-oster/VisiCut/wiki/Supported-Hardware page and then throw a large celebration party. :tada: :balloon: :balloon: :balloon: :balloon: Happy to see the fablabnbg changes (mostly) merged back in....

Current status: Time estimation is supported by most drivers. Can be added easily to new drivers, see https://github.com/mgmax/LibLaserCut/commit/0b63d63b119a399073217487eb8aa7f16533e372 .

Current status: You can set the desired number of digits in the lasercutter settings for most GCode-based lasercutters. The default is 6 (which we should probably change to 3).

I am closing this PR because it unfortunately got stuck unfinished. Feel free to open a new PR against the latest version. Thank you for your time and understanding.

You could reuse code from the dummy driver, which has a SVG export and playback functionality: https://github.com/t-oster/LibLaserCut/blob/develop/src/com/t_oster/liblasercut/drivers/Dummy.java

Yes, it's a software bug: A start point which isn't top-left of the drawing, but inside, is not correctly implemented in our Epilog driver. I'd guess you are the first...

At least on an Epilog Zing with newest firmware, I could not reproduce the bug. However the bug may occur with other models or firmware versions.

Yes, cutting works despite the warning. Unfortunately I did not test engraving.