-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Porting geometry.t to catch #36
Comments
All of the tests that don't need anything extra translated are done and passing. I took a look at most of the code that I will need to translate and tried to understand how it works and where it is used.
@lordofhyphens, any suggestions on how to test to confirm that they are actually never used anywhere in the code? |
For figuring out if it's used or not, grep is probably the one-off "hey who calls what" I'd use, working your way up the call stack. For things on the perl side, you'd want to check the xsp files if you suspect it's in libslic3r. There are commercial programs for doing source code analysis (Understand from SciTools is one my coworkers use). AFAIK the arc fitting code isn't used in Slic3r anymore (it was for G2/G3 gcode generation). |
The arc fitting still has a config option to turn it on, but upon trying to export gcode, it fails. I took a close look through Geometry.pm to see what methods are completely unused. More than half is completely unused. ArcFitting.pm is then uses a few methods otherwise not called. Aside from methods used only by ArcFitting.pm, only Line::grow is left to get the test working on. |
I'd leave them be for now, then. Paste the unused functions into Geometry.cpp and comment them out (with |
Didn't get much done today, but the tests are all converted besides the unused methods and |
Part of working on #33
I've got a solid start on converting it. Many of the basic tests that are already supported by libslic3r have been ported and confirmed to work. I haven't translated anything into libslic3r yet though.
The text was updated successfully, but these errors were encountered: