UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
debugging is a pain, open cura, "execute" the PPS, see the result, close cura, modify the PPS, open cura, "execute" the PPS, see the result, close cura... so boring.
Is there no support anywhere to deal with this ungodly cycle of modify the Python code, double-click on an STL to load up Cura, go get a coffee or something because Cura is DEATHLY slow, slice, check results, close Cura, lather, rinse, repeat. Surely we can't be the ONLY people who think that this is a REALLY crummy way to test and debug code.
What is the correct development cycle to develop, test, and debug post-processing Python scripts?
Manual for developing cura plugins
in UltiMaker Cura
Posted
Is there no support anywhere to deal with this ungodly cycle of modify the Python code, double-click on an STL to load up Cura, go get a coffee or something because Cura is DEATHLY slow, slice, check results, close Cura, lather, rinse, repeat. Surely we can't be the ONLY people who think that this is a REALLY crummy way to test and debug code.
What is the correct development cycle to develop, test, and debug post-processing Python scripts?