Andrey Zabolotnyi wants to merge 5 commits from /u/andyz/dxf2gcode/ to develop, 2020-02-04
I noted one of my patches were reverted.
I checked and didn't found why.
If I re-apply the patch on upstream develop branch, all tests would pass except "top.dxf", which crashes dxf2gcode. I fixed that bug as well. Now (with the proposed patch) all tests pass:
Ran 73 tests in 1477.453s
OK
I'll explain what the patch fixes (how to reproduce the bug and how to check my patch fixes it).
Commit | Date | |
---|---|---|
[4da0a9]
(upstream-fix-gcode-export)
by
![]() Fixed a bug in latest changes that manifests itself only with the 2D driver. |
2020-02-03 20:18:38 | Tree |
[a632b5]
by
![]() Now after "set nearest point" operation the start moves will be correctly updated on the drawing |
2020-02-01 22:51:52 | Tree |
[086590]
by
![]() Fixed a old nasty bug that would cause broken G-code export after invoking Shape.setNearestStPoint() |
2020-02-01 22:20:20 | Tree |
2020-02-01 21:31:30 | Tree | |
[706ed1]
by
![]() Replaced __str__ with __repr__ which is similar, but allows printing lists of objects as well |
2020-02-01 21:30:34 | Tree |
Andrey,
You may find the explanation of the revert in the commit message, see below:
As you could see it broke almost all of tests at that time.
Unfortunately when I try to test your changes I still see errors like below:
The final test result is:
I'm using fedora 31 with:
Please also notice the difference in the number of tests. You mentioned 73 while on the develop branch (at the time of writing) we have currently 76 tests available . It looks like you're not testing against the latest version of the develop branch.
hmm... If I check-out a clean repository:
perhaps, you have 3 uncommited dxf files...
I'm on Fedora27 with
python3-3.6.6-1.fc27.x86_64
python3-qt5-base-5.9.1-3.fc27.x86_64
which shouldn't make difference...
Now I apply the proposed patch:
The run the test on 1.dxf, as in your log above:
dxf2gcode_test.py also runs almost ok:
the problem with DRAAK.dxf is some other problem, never seen it before:
Could you try with a clean repository like I did above?
I found what's wrong. I'm using the 3D driver and you're using the 2D one :)
After I changed the option, I get the crash too.
The reason is that I added StMove::update method, and StMoveGUI in 2D driver uses update() method as well, so they conflicted.
Latest fix should fix it all.
Indeed, great!
I can confirm no regressions on 4da0a94e082edca5e9b23c5cc2bef63e44e2dce1.
Thank you all for this support ...